Online forecasting system and method

ABSTRACT

System and method for real-time on-line interactive forecasting of an element, the method comprising: receiving a user input for a forecast element; and capturing at least one forecast of an element or event, storing that at least one forecast of an element or event, and sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display. The method may optionally also include either or both of providing a minimal input forecast interface, and/or pre-queuing a list of elements for fast forecasting; receiving a user input for a forecast element. Computer program product for execution on a single computer or plurality of computers to implement the inventive method and system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 11/540,944 filed Sep. 29, 2006, now U.S. Pat. No. 7,451,213, entitled Online Forecasting System and Method, by Craig K. Kaplan, which claims the benefit of priority to U.S. Provisional Application Ser. No. 60/722,099, filed Sep. 30, 2005, entitled Improved Online Forecasting System, by Craig A. Kaplan, each of which applications is hereby incorporated by reference.

FIELD OF THE INVENTION

This invention pertains generally to systems and methods for on-line prediction and forecasting and more particularly to an interface for a one-click graphical interface for making future predictions or forecasts for an element where receipt of the one-click input by the system results in capturing a forecast of an element or event, storing that forecast of the element or event, and optionally the display of collective contributed forecast information back to the user who originally made and sent the input.

BACKGROUND

As described in co-pending U.S. Utility patent application Ser. No. 10/107,420 filed 26 Mar. 2002 and entitled System and Method for Forecasting Information Using Collective Intelligence from Diverse Sources (which application is incorporated by reference herein), it is possible to construct a real-time forecast system that includes: (a) means for gathering forecasts from a plurality of individuals or other entities within a defined period of time; (b) means of filtering and processing these individual forecasts to generate a collective forecast, and (c) means for communicating the collective forecast back to individuals very quickly.

However, even such a forecasting system generally operates with greater prediction or forecasting accuracy as greater numbers of forecasts are gathered from users (also referred to as contributors). Users, in turn, are more likely to provide a larger number of forecasts if one or more of and preferably all of the following are true of the system: (a) the system is very easy to use initially; (b) the system already has some forecasts or predictions at the time the user first uses the system; and (c) the system becomes even easier to use (or more useful with ease of use) upon repeated use.

Therefore, there remains a need for a system and method for forecasting that encourages new and previous users to continue to utilize such a forecasting system and method of forecasting by making it easier to use and contribute to such forecasts so that larger numbers of forecasts may be obtained and the forecasting accuracy may increase to the extent possible by the increased participation and number of contributions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration showing an exemplary embodiment of a system according to the invention.

FIG. 2 is an illustration showing a display screen and the appearance of an embodiment of the one-click rating scale prediction interface.

FIG. 3 is an illustration showing a portion of the one-click rating scale prediction interface in FIG. 2.

FIG. 4 is an illustration showing a method for real-time on-line interactive forecasting of an element according to an embodiment of the invention.

SUMMARY

In one aspect the invention provides a method for real-time on-line interactive forecasting of an element, the method comprising: providing a minimal input forecast interface; receiving a user input for a forecast element; and capturing at least one forecast of an element or event, storing that at least one forecast of an element or event, and sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display. The method may optionally also include pre-queuing a list of elements for fast forecasting; receiving a user input for a forecast element.

In another aspect, the invention provides a method for real-time on-line interactive forecasting of an element, the method comprising: pre-queuing a list of elements for fast forecasting; receiving a user input for a forecast element; and capturing at least one forecast of an element or event, storing that at least one forecast of an element or event, and sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display. The method may optionally also include providing a minimal input forecast interface.

In another aspect, the invention provides a system for real-time on-line interactive forecasting of an element, the system comprising: a minimal input forecast interface; a receiver block for receiving a user input for a forecast element; a capture block for capturing at least one forecast of an element or event; a storage device for storing that at least one forecast of an element or event; and communications device for sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display. This system may optionally further include or provide a minimal input forecast interface.

In another aspect, the invention provides a system for real-time on-line interactive forecasting of an element, the system comprising: a pre-queuing block for queuing a list of elements for fast forecasting; a receiver block for receiving a user input for a forecast element; a capture block for capturing at least one forecast of an element or event; a storage device for storing that at least one forecast of an element or event, and communications device for sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display. This system may also optionally further include a pre-queuing block for queuing a list of elements for fast forecasting.

In another aspect, the invention provides for separate client side and server side method steps and computer program product elements separately and in combination.

In another aspect, steps of the various embodiments of the method may be incorporated into the system by any hardware, software, firmware, or hybrid means to implement the inventive steps in the system.

In another aspect, the invention provides a computer program product stored on tangible media or residing in an electronically readable and accessible form, the computer program product including executable instructions for modifying the operation of a single computer or a plurality of computer to operated to provide a real-time on-line interactive forecasting of an element, the computer program instructions including instructions for: either: (i) providing a minimal input forecast interface, or (ii) pre-queuing a list of elements for fast forecasting, or both; receiving a user input for a forecast element; and capturing at least one forecast of an element or event, storing that at least one forecast of an element or event, and sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

In general, the more work a user has to do to get a useful result from a system, the less likely a user is to the use the system. In the system described in co-pending referenced U.S. Utility Patent Application System and Method for Forecasting Information Using Collective Intelligence from Diverse Sources referenced herein, system and method are described wherein users were asked to type in specific forecasts (e.g., closing prices for stocks) for particular times and dates in the future. This approach has the advantage of precision, and in some cases may be the preferred implementation of a forecasting system and method. However precision may at times for some users come at the cost of ease of use. Increasingly for many computer and information related tasks a graphical or non-text type input mechanism may be preferred.

FIG. 1 shows an exemplary embodiment of a system 51, incorporating a server 52 that may serve to interact with one or more users 54 over an interactive electronic medium such as computers 56 or other information appliances coupled to the server 52 over a network 60 such as the Internet. Network, server, and computer and communications links that are conventional in nature and not shown in the figure to avoid obscuring aspects of the invention.

The server 52 may include one or more processors 72 and processor coupled or associated memory 73 for any processing tasks that may be required. Such processing tasks may include controlling communications over the network to and from users, accessing one or more integrated or separate storage devices 74 such as for example hard disk drive persistent mass storage devices that may store programs, forecast data, element current values and historical values, and other system and user data described herein. Processing may also include activities of intelligent agents 75 (described in detail herein) and activities in support of processing user contributed forecasts or predictions to generate output composite or consensus forecasts or predictions as described herein elsewhere.

A user may access the server from a client side computer or information appliance (machine) 77 over the network communication link or line 78. The user may be provided with a computer program code or applet to display and execute the one-click scale forecasting interface on their machine. Local storage may be provided on the local user computer or information appliance for storing a token, cookie, or other identifier so that past predictions and forecasts, favorites, lists, queues, and the like that are usefully provided and associated with the user and with the user's forecasting or prediction history may be stored and communicated to the server and to programs executing on the server as appropriate.

Although a single server is illustrated, the functions and operations performed by the server may be distributed over a plurality of servers either for the purpose of scalability, redundancy, performance or for other reasons.

Exemplary One-Click Rating Scale Forecasting Interface

In one non-limiting embodiment of the inventive system and method, the invention includes a one-click forecasting interface. With reference to FIG. 2, in at least one embodiment, the one-click forecasting interfaces 101 is coupled with a rating scale 102 having a plurality of values 104-N so that a user or contributing forecaster 106 merely needs to look at the one-click rating scale interface, such as a one-click rating scale forecasting interface 101 on the display screen 108, place a mouse tip (or other pointing or positioning device pointer) 110 on the rating scale and make a single input, such as right or left mouse button clicking, to input the forecast 120. Keystrokes may alternatively be used, as may a mouse (or other pointing device input) click coupled with a keystroke or some other minimal action different from actually typing a recognizable text or symbol string for a name or other identifier.

FIG. 3 illustrates the rating or input rating scale nature of one non-limiting embodiment of the interface in somewhat greater detail than may be seen from FIG. 2. In this particular illustration, the element that is to be rated for a change in value is the Dow Jones Industrial Average which at the time was at a value of 10,542.83 at 113, representing a −0.09% change at 114, and with the interface asking for a prediction of “Monday's Close:???” at 114. The interface includes a plurality of values 104-N with fixed or constant rating scale value increments or values, here shown 104-1 through 104-11 as −10%, −5%, −2%, −1%, ±0%, +1%, +2% +5%, and +10%. These values are merely illustrative and it will be apparent that any values may be used and that the scale may be linear or non-linear. Actual dollar value changes might be made for stock indexes, stock prices, or the like rather than percentage changes and/or a user may input a preference via a toggle or menu item. The user contributing forecaster may optionally merely click on the downward pointing arrow (red) 111 to make a prediction that the Dow Jones Industrial Average will go down, or click on the upward pointing arrow (green) 112 on the right to make a prediction that the Dow Jones Industrial Average will go up. The increments may be somewhat context sensitive so that they represent a reasonable range for upward or downward movement of the element based on some factor or set of factors, such as for example based on its historical trading range, recent predictions or forecasts by others, or on other factors.

Notice that in this non-limiting embodiment, the interface 101 also provides a clickable hover or hot spot for the user to select to see additional details 115 and to see a listing or the users stocks “Your Stocks” 116. These hot spots or menu items may change with the type of element displayed for prediction at the time.

Typing may for most users computer and/or information appliance require more effort than clicking a mouse or using some other pointing device to make an input. Moreover, requiring users to perform multiple actions (such as for example, typing one or more places or locations in an electronic form or web page and then clicking submit) requires more effort than a single mouse click. Furthermore, as input devices become more diverse, smaller, and may loose a full text keyboard or symbol input capability, other simpler forms of input may be more widely supportable. Graphical interfaces may also be preferred because of their intuitive nature over interfaces for which textual inputs or keyboard typing are employed, but embodiments of the invention are not limited to particular interfaces, except that interfaces that simplify user interaction such as a single-click interface are preferred. To maximize ease of use, this embodiment of the invention has a single-click rating scale based interface to the forecasting system. In a non-limiting embodiment, a single-click interface captures a single forecast of an element or event, stores that forecast, and displays useful collective forecast information back to the user all with a single click. Because user effort is minimized, and because feedback is almost immediate, the single-click rating scale interface helps maximize the number of forecasts per user. In some situations, though perhaps not all situations, maximizing the number of forecasts per user may often be an important goal.

Although single-click interfaces (such as the Amazon single-click ordering interface control described in U.S. Pat. No. 5,960,411, and less famously this inventor's 1994 patent (U.S. Pat. No. 5,280,275) entitled Graphical Interface Control Buttons With Scalar Values) have been used before for making purchases, this is the first time that such a single-click interface control has been used in conjunction with a forecasting system that initiates all of the actions required for accepting, storing, generating, and displaying a collective forecast. It may also be appreciated that the interface actually provides for a selection and click feature since by single-clicking on the values (discrete or continuous range based scales may be used) of the scale the user is actually inputting a predictions (such as a quantitative numerical prediction) and need not type the prediction or forecast before making the one input action. The single-click forecasting interface initiates the acceptance, storing, generation, and optional but advantageous display of the collective forecast. Even for one click purchasing systems and method, the user must by separate action, identify the goods or services that the user desires to purchase and then make a separate action to complete the purchase, not even including the need to complete a prior name, address, and credit card or other purchasing information prior to the click-based order completion. It will be appreciated where it is impractical or for other reasons not advantageous to provide a single-click interface, then reducing or minimizing the number of clicks or user actions is advantageous so that other embodiments of the invention may provide for two-click, three-click or other multiple-click interfaces.

Intelligent Agents to Ensure Multiple Forecasts & Encourage User Participation

In at least one non-limiting embodiment, the use of intelligent agents is employed to motivate users to make their own predictions and to ensure multiple forecasts for an element and to encourage user participation. It may be appreciated that a common concern of users who are considering whether to enter their own forecast information for the first time is whether they will get useful information back from the system and whether their time will be well invested or wasted. For example, if no other users have forecast on a particular element (such as for example on a particular stock), prospective contributing users may be less inclined to enter their own forecasts since the collective forecast they receive in return has no information other than what they themselves entered.

To at least partially solve this problem, it is optional but advantageous to seed or initialize the system with useful initial forecasts when few or no such forecasts exist. However, for systems and methods attempting to forecast on a large number of elements whose values are changing constantly (such as changing in the way stock prices change), seeding the system with useful initial forecasts that are recent and timely may become a significant problem.

One solution to this potential problem is to use intelligent agents that can forecast on demand. By constructing non-human intelligent agents (such as agents implementing artificial intelligence or AI capabilities) that have been programmed to follow one or various forecasting philosophies, rules, or policies; and, by programming agents to forecast on demand (e.g., on the same stocks and at almost the same time as human forecasters) it is possible to guarantee that every human forecaster will always get a collective forecast that includes forecasts other than his or her own, even if sometimes this means the other forecasts are from non-human intelligent agents rather than from other humans. The on-demand forecasts may be triggered by a user and potential forecaster accessing the system and identifying an element of interest (such as a stock of interest) or the on-demand forecast by the intelligent agents may wait for the user to provide their forecast input as the trigger to the agent forecast. Non-limiting embodiments of the invention may provide for either a single or a plurality of intelligent agents may be marshaled for the forecast, and when a plurality are marshaled they may be programmed with different forecasting philosophies, rules, or policies that represent a range of the perspectives and approaches that might be taken by human forecasters. The actual number may and choice of different forecasting philosophies, rules, or policies may be selected based on statistical considerations, human behavior considerations, the type of element being forecast, or some combination of these factors alone or in conjunction with other factors.

Because the weight of agents' predictions may advantageously be adjusted or modified based on performance, agents do not introduce undue or significant noise or error into the system, and, in some cases may even improve upon what human forecasters are able to do. Weighting forecasts based on prior objective forecaster performance is described in the referenced co-pending U.S. Patent Application System and Method for Forecasting Information Using Collective Intelligence from Diverse Sources, which is hereby incorporated by reference, and may optionally but advantageously be applied. In one embodiment, non-uniform weightings are applied to different forecasts and the weight applied to intelligent agent generated forecasts may be adjusted to diminish over time, to decrease to zero after a certain number of human forecasts have been received, or to otherwise be modified or changed in a predetermined or dynamically determined manner specified rules or policies established for that purpose.

In one preferred implementation or embodiment, users of the inventive system and method may choose how many, if any, non-human agent predictions to include in any given collective forecast so that the effect of the artificial intelligence based non-human agents can be understood and separated from the human collective intelligence if desired. In one embodiment, where some predetermined or dynamically determined percentage or absolute number of forecasts are made by one or more non-human agents, the user may be informed of that circumstance.

Exemplary Intelligent Queuing Capability

Non-limiting embodiments of the invention may optionally but advantageously provide an intelligent listing or queuing capability. Beyond securing user participation during the initial forecasting session, a well-designed forecasting system may advantageously make it easier for repeat visitors or repeat users to enter their forecasts. Moreover, since a users' time is or may be limited, whenever possible, the system should advantageously be designed to elicit the most valuable forecast information first—before users run out of time or attention. A known technique that can be used as a motivator in this regard is to allow users to select the elements (such as for example, stocks) for which they would like to forecast. The forecasting system described in the System and Method for Forecasting Information Using Collective Intelligence from Diverse Sources patent application, at least partially accomplished this goal by allowing users to type in the elements such as by using text names, stock symbols, or the like, for which they wanted to make forecasts. A disadvantage or drawback of this earlier system and method, however, is that typing (especially more than a few characters) takes more user effort than pointing or positioning a mouse and clicking a mouse button, or the equivalent with trackballs, capacitive or other finger-pad, or other pointing and button-like selection devices commonly found on desktop computers, notebook computers, personal data assistants (PDAs), cellular telephones, and the like information appliances. Moreover, if the user does not know the correct element (e.g., stock symbol) to type in, the user may usually need perform the additional task of a “symbol lookup” or the equivalent or analogous additional action for some other non-stock element to forecast. Such additional tasks may ultimately discourage at least some users and undermine the desire to increase the number of forecast contributions.

One alternative is to allow users to select elements (e.g., stocks) or groups of elements from a list by clicking a mouse. However this solution may also tend to consume valuable screen real estate and may have a limited ability to scale to screens of different sizes or to larger or smaller characters or symbols, or otherwise present scalability issues.

The present invention minimizes user effort by providing a default list of elements, that are advantageously pre-queued, for fast, single-click (or minimum click or user input involvement) forecasts. (In the stock forecasting domain, this approach is different from but at least superficially analogous to the system choosing a hidden default watch list whose elements will be revealed one at a time as the system solicits user forecasts.) The advantage of ease of use and speed for the user comes at the cost of predetermining what elements users will see. If users are unfamiliar with the element chosen by default, they may know nothing or very little on which to base their forecasts.

To address this problem and to provide a useful solution to it, the present invention also allows users to optionally override or modify the default element list (e.g., “hidden watch list”) by typing in elements (e.g., stock symbols) after the manner of the system and method described in the System and Method for Forecasting Information Using Collective Intelligence from Diverse Sources patent application. However, whereas users of that earlier system would register (registration is additional work that some users are particularly loathe to do) in order for the system to remember their “watch list”, in one embodiment of the invention the system and method automatically remembers each users' preference of elements using a cookie. The generation of useful Internet or web browser cookies are know in the art as are method for making and storing such cookies on a computer or information appliance. Other embodiments may use registration of some type, address information, or other use recognition or identification means where a user may either prefer not to store a cookie or where a cookie has been deleted. For returning users, the cookie (or other user identification means) tells the system to display the elements that users have previously typed in (e.g., their “watch list” stocks)—before elements on the default list. Thus in at least some non-limiting embodiments of the invention, the system and method maximize or at least attempt to maximize the potential usefulness of user forecasts by remembering the history of each user. In at least some embodiments, the user may be provided with an option to delete or purge all or part of their history.

It is possible to increase the usefulness of the information from users even further by optimizing the position of elements in the queue or information data structure based on other information, such as the forecast history for each element, not just a history of which elements were selected.

In experimental testing of the system and method, these novel elements—the one-click rating scale forecasting interface, the intelligent agents, and the intelligent queuing capability—individually and in combination, have led to significant benefits over previous forecasting system designs and forecasting methods.

It will be appreciated in light of the description provided herein that many variations of these exemplary embodiments and implementations are possible. The features and elements to be included in a particular implementation may depend at least in part upon the goals and objectives of different users and/or providers of the inventive system and method, therefore various features, elements, and options are described in the sections to follow.

Exemplary Adaptive Variation of One-Click Rating Scale Forecasting Interface

By way of example and not limitation, with respect to the exemplary one-click forecasting interface illustrated in and described relative to FIG. 1 and FIG. 2, a one-click rating scale with fixed or constant value labels is provided. In one non-limiting embodiment, the constant value labels are selected as −10%, −5%, −2%, −1%, 0, +1%, +2%, +5%, +10% and the like, though any value labels may be provided. As a variation, it will be appreciated in light of the description provided here that a computer programmer having ordinary skill in the art, in light of the description provided herein may readily adapt the exemplary embodiments and implementations illustrated and described herein to provide for a one-click rating scale that does not have any labels, or that has labels only at the extremes of the scale, or other non-label indicators.

An advantage of the fixed or constant label scheme that we have illustrated in the exemplary embodiment of FIG. 1 and FIG. 2, is that the user knows exactly what his or her click means in terms of providing forecast input to the system. However a possible disadvantage of such constant label scheme in some circumstances is that different users typically have different characteristics when it comes to clicking rating scales. Some users may be conservative and rarely use the extremes of the scale. Other users may be expressive and rarely use the center of the scale. Such differences between users are well documented in the rating scale literature.

One alternative approach to providing fixed or constant labels on the rating scale is to have the system dynamically and/or adaptively calibrate or modify the rating scale for each user on any one or more of various calibration or adjustment factors so as to maximize the accuracy of past predictions. In such an embodiment, a user may click on the rating scale without labels being shown (or with only the extremes of the scale labeled), or on up, down or unchanged indicators as may be appropriate. Adaptive algorithms, using statistical techniques known in the art, would determine an optimal labeling that might be referred to as an “invisible labeling” for each user's clicks that would compensate for the fact that each different particular user is likely to click on a scale differently, even when given the same information. The “invisible” adaptive labels need not actually be shown on the scale, but the system would know the adaptive values and use those adaptive values when tabulating the inputs from each user. Optionally, the user may be provided with a display of the value or forecast that was input, separate or apart from the labels.

Exemplary Variations on Intelligent Agents

With regard to the intelligent agents, variations may also or alternatively be provided and it will be apparent in light of the description provided herein that the intelligent agent or agents that provide the afore described seed or initial forecasts may be implemented as computer programs and that the particular philosophies, rules, policies, or the like that such intelligent agents are programmed with may be selected as desired. By way of example but not limitation, intelligent agents that mimic some of the popular strategies of traders (such as for example, so called “momentum trading” or other trading strategies) as well as some intelligent agents that provide a baseline for measuring human performance (e.g., the “flip a coin and guess” agent). Embodiments of the invention that provide intelligent agents that may not even utilize much intelligence, such as a random selection based agent, may be utilized, but are not preferred. One embodiment of an exemplary intelligent agent is set forth in the exemplary pseudo code for a prediction agent in Table I (See Appendix of Tables). The exemplary pseudo code is for prediction agents running Dow Jones Industrial Average (“Dow”), NASDAQ, Standard & Poors 500 (“S&P 500”) predictions or forecasts. These agents take into account whether or not predictions have been made within a certain time period of the present time.

Another useful class of non-human agent variations is to use intelligent agents that generalize from the successful predictions of humans (or any other agents) on a limited set of elements to a larger set of elements. For example, in the domain of stock price forecasting, a relatively large number of humans may forecast the movements of the NASDAQ index, but few or no humans may forecast stock price movements for a small technology company. A simple or crude agent might be programmed to forecast according to the theory that when accurate humans forecast the NASDAQ to increase, the agent should forecast that the stock price for small technology companies (perhaps those without any human predictions) will also go up. If this simple or crude generalization agent does well, then the weighting algorithms (known in the art or such as specified in the referenced System and Method for Forecasting Information Using Collective Intelligence from Diverse Sources patent application) will give it significant weight. Otherwise its input will be obscured by more accurate agents or humans. It will be apparent in light of the description provided herein that many variations of generalization agents can be constructed and allowed to compete amongst themselves and/or with other human forecasters.

Exemplary Variations on Intelligent Queuing Capability

The intelligent queuing capability and/or format of the intelligent queue may also or alternatively varied. As described elsewhere herein, if it is desired to improve or indeed to maximize or attempt to maximize the useful information from system users in the minimum amount of time, then it makes sense to ask for forecasts (e.g., price forecasts for stocks) where users are likely to have the most information first. To this end, in one exemplary but non-limiting embodiment of the improved forecasting system and method, the forecasting system and method remembers, via a cookie, the forecasts that users made in the last (or other previous) time, and displays these same items (e.g., stocks) to get new forecasts the next time the same user uses or accesses the system. Other data sets, tokens, storage methodologies, or identification schemes or techniques may be utilized where the use of cookies does not provide a preferred approach either due to security issues or user computer preferences against storing cookies on their computer or other information appliance with which the user accesses the system.

This method is superior to simply requesting forecasts on elements (e.g., stocks) in a random or a set order since users who have predicted or forecast specific elements (e.g., stocks) in the past are likely to have useful information about those same elements in the future, at least for some reasonable future period. This method also has the virtue of being simple and easily understandable by users, because they are familiar with other types of systems that remember lists of things for them in the order in which they first created or encountered the list (e.g., “watch lists”).

However, it is also possible to optionally construct variations of the intelligent queuing scheme that not only remember which elements (e.g., stocks) users predicted a last or other previous time or session, but also or alternatively to reorder the elements so as to obtain the most information from the user in the least amount of time.

In one non-limiting embodiment, recent symbols, favorite symbols, processing or lists, and generation and handling or cookies are taken care of in software, such as by computer program software of the type listed in Table 2 (See Appendix of Tables) for Exemplary Code for Recent and Favorite Symbols. Table 3 (See Appendix of Tables) includes a listing of exemplary computer program code for an exemplary interface.

The historical forecasts that users made may be used to reorder the queue of symbols (or other information indicators) which the system remembers via a cookie or via other means. For example, in the domain of stock forecasting, the most common forecasts for any given stock are typically for small change or no change in stock price. Because these forecasts are most likely, the information content (as can be proved from theorems in Information Theory) is less than the information contained in more extreme forecasts.

In other words, generally, the more extreme the forecasts are, the more information those forecasts may contain. Thus, one way to maximize the useful information obtained by the system in the shortest time is to look at all of the stock symbols for which a user has made forecasts in the past (e.g., those remembered by the cookie) and then order these stock symbols so that the symbols with a history of more extreme forecasts are placed first in the queue. When a user returns to the site, not only will the system remember which symbols the user predicted or forecast on before, but also the system will present these symbols in an order so that those symbols where the user historically has made the most extreme predictions come before symbols with less (historically) extreme predictions. The result is the maximum information obtained from the user in the minimum amount of time.

Other intelligent queuing variations are also possible and may additionally and/or alternatively be implemented, using a variety of techniques that will be apparent to computer programmers having ordinary skill in the art in light of the description provided herein. Again using stock forecasting as an example domain, a user may have a short queue of symbols that he or she has typed in or otherwise provided, or may even have no user-entered queue at all. Still the system can attempt to re-order the default queue of symbols based on some set of rules, policies, or procedures, such as for example by using category analysis and/or statistical associations derived from that particular user and/or all users of the system.

Specifically, consider the case where a user has made extreme predictions on several technology stocks that all are traded on NASDAQ. (An exemplary prediction of this type may for example be a prediction containing large amounts of information in an Information Theoretic sense where information is correlated with the rarity of events.) NASDAQ is a common category that links forecasts containing high amounts of information for this user. In one non-limiting embodiment, the inventive system and method may intelligently reorder a default queue (and/or the queue of stocks remembered by a cookie or other means) to display NASDAQ stocks first for this user, since that is likely to be the best strategy for obtaining the most information in the shortest amount of time from this user.

Consider another case, still in the stock forecasting domain. For purpose of explanation but not as a limitation of the invention, assume that across all users, the system calculates that users who forecast or predict accurately on Yahoo are also likely to forecast or predict accurately on Google and Ask Jeeves (all Internet search companies). The system can then proactively reorder, or insert, Google and Ask Jeeves, in the queue of stocks being presented to a user who says that she/he wants to forecast a future state or stock for Yahoo. The user does not need to type in symbols for Google and Ask Jeeves. The system intelligently determined or calculates that Google and Ask Jeeves should be presented to this user because other users who predicted on Yahoo typically also had accurate forecasts Google and Ask Jeeves. This intelligent determination or calculation may be based on or utilize any one or combination of statistical algorithms well known in the art,

This approach is at least superficially somewhat similar to the collaborative filtering methods used by Amazon, NetFlix, and others in which products are recommended based on “what other users who bought your product also liked.” However, one key difference is that in the present invention, elements are not recommended; they are inserted and/or re-ordered in a queue or other data structure. Furthermore, in at least one non-limiting embodiment, the basis for the insertion, ordering, or reordering is not whether someone liked an element but rather how well they performed on a given task—in this case predicting or forecasting.

The logic is: “Other people who forecast well on ABC also tended to forecast well on XYZ.” By quantifying the correlation between ABC and XYZ it is possible to determine not only whether XYZ should be shown to someone forecasting on ABC, but also when (e.g., where in a list) XYZ should be located, ranked, or shown.

The result of this and the other innovations described above is that the inventive system and method obtains the maximum useful information with the minimum of time and effort from the user. The inventive method may be implemented as a computer program executing within a processor and memory of a general purpose computer (such as of a server computer).

Having now described numerous aspects and embodiment of the invention including many optional features, attention is directed to the description of certain selected embodiments that include particular combinations of features.

In one embodiment, the invention provides a method for real-time on-line interactive forecasting of an element, the method comprising: providing a minimal input forecast interface; receiving a user input for a forecast element; and capturing at least one forecast of an element or event, storing that at least one forecast of an element or event, and sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display. This embodiment is illustrated in FIG. 4.

In another embodiment (2), this method further comprises displaying or causing the display of the collective contributed forecast information sent to the user.

In another embodiment (3), this method further comprises generating at least one forecast for an element (for a plurality of elements) using a non-human intelligent agent programmed to follow a predetermined or dynamically determined forecasting philosophy, rule, or policy; and seeding a particular forecast element with the at least one generated forecast when no prior forecast for the particular forecast element exists at the time a human contributor contributes a forecast or requests forecast information for the particular element.

In another embodiment (4), this method further comprises sending the user a consensus forecast generated from a plurality of user contributed forecasts for the same element for which the user forecast was received, the sending being in response to and substantially in real time with the receipt of the forecast submission by the user.

In another embodiment (5), this method further requires that the pre-queuing a list of elements for fast forecasting is in order to solicit a predetermined set of identified valuable information as a priority over other information and providing an override capability.

In another embodiment (6), this method further requires that the minimal input forecast interface comprises a one-click scale forecasting interface.

In another embodiment (7), this method further requires that the minimal user input interface consists of a single-click scale forecasting interface.

In another embodiment (8), this method further requires that the pre-queuing of a list of elements for fast forecasting comprising pre-queuing the list of elements for fast one-click interactive forecasting.

In another embodiment (9), this method further requires that the minimal user input interface comprises a single-click interface in combination with a scale for generating a numerical value input as a result of the single click, the value depending upon the location of a graphical on-screen pointer or icon for determining the numerical value, and the value changing with the location of the screen pointer or icon on the display screen.

In another embodiment (10), this method further requires that the method further comprises providing adaptive variation of the one-click rating scale forecasting interface.

In another embodiment (11), this method further comprising dynamically and/or adaptively calibrating or modifying the scale for each user so as to improve the accuracy of predictions and forecasts.

In another embodiment (12), this method further requires that (a) the system is easy to use initially; (b) has some forecasts at the time the user first uses the system; and (c) becomes even easier to use upon repeated use.

In another embodiment (13), this method further requires that a single user input action based interface captures a single forecast of an element or event, stores that forecast, and displays useful collective forecast information back to the user all with a single click.

In another embodiment (14), this method further requires that a single-click interface captures a single forecast of an element or event, stores that forecast, and displays useful collective forecast information back to the user all with a single click.

In another embodiment (15), this method further requires that user effort is minimized by the forecast input interface and user feedback in response to the one-click input is almost immediate so that the single-click rating scale interface and substantially immediate consensus forecast feedback helps maximize the number of forecasts per user.

In another embodiment (16), this method further requires that the interfaces is provided in a forecasting system that initiates all of the actions required for accepting, storing, generating, and displaying a collective forecast.

In another embodiment (17), this method further requires that the at least one non-human intelligent agents is a computer implemented artificial intelligence based agent.

In another embodiment (18), this method further requires pre-queuing a list of elements for fast forecasting.

In another aspect, the invention provides a method (19) for real-time on-line interactive forecasting of an element, the method comprising: pre-queuing a list of elements for fast forecasting; receiving a user input for a forecast element; and capturing at least one forecast of an element or event, storing that at least one forecast of an element or event, and sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display.

In another embodiment (20), this method further requires providing a minimal input forecast interface.

In another aspect, the invention provides a system (20) for real-time on-line interactive forecasting of an element, the system comprising: a minimal input forecast interface; a receiver block for receiving a user input for a forecast element; a capture block for capturing at least one forecast of an element or event; a storage device for storing that at least one forecast of an element or event; and communications device for sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display.

In another embodiment (21), this system further includes a minimal input forecast interface.

In another aspect, the invention includes a system (22) for real-time on-line interactive forecasting of an element, the system comprising: a pre-queuing block for queuing a list of elements for fast forecasting; a receiver block for receiving a user input for a forecast element; a capture block for capturing at least one forecast of an element or event; a storage device for storing that at least one forecast of an element or event, and communications device for sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display.

In another embodiment (24), this system further includes a pre-queuing block for queuing a list of elements for fast forecasting.

In another aspect, the invention includes a computer program product stored on tangible media or residing in an electronically readable and accessible form, the computer program product including executable instructions for modifying the operation of a single computer or a plurality of computer to operated to provide a real-time on-line interactive forecasting of an element, the computer program instructions including instructions for: either: (i) providing a minimal input forecast interface, or (ii) pre-queuing a list of elements for fast forecasting, or both; receiving a user input for a forecast element; and capturing at least one forecast of an element or event, storing that at least one forecast of an element or event, and sending collective contributed forecast information back to the user who originally sent the input in response to the receipt of the user input for optional display.

Headers and sub headers provided in this specification are merely provided as a guide to the reader as to the primary description provided in that section. As aspects of the invention and its embodiments are described throughout the specification and in the drawings and claims, these headers and sub headers should not be used to limit the scope of the invention in any way.

As used herein, the term “embodiment” means an embodiment that serves to illustrate by way of example but not limitation.

It will be appreciated to those skilled in the art that the preceding examples and embodiments are exemplary and not limiting to the scope of the present invention. It is intended that all permutations, enhancements, equivalents, and improvements thereto that are apparent to those skilled in the art upon a reading of the specification and a study of the drawings are included within the true spirit and scope of the present invention. It is therefore intended that the following appended claims include all such modifications, permutations and equivalents as fall within the true spirit and scope of the present invention.

COPYRIGHT NOTICE

Contained herein is material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction of the patent disclosure by any person as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights to the copyright whatsoever.

APPENDIX OF TABLES

TABLE 1 Exemplary Code for Prediction Agents (all agents.sql) -- Copyright 2005 iQ Company -- -- Usage: --  EXEC spAgentsRunSomeIfNecessary IBM, ‘9/30/2005 4:00:00 PM’, ‘9/30/2005 12:00:00 AM’ -- --  (Final parameter, @PriorRunDateTime, is optional and defaults to 12 AM on the current day.) -- -- Results: --  Runs predictions agents. If no agents have runs since @PriorRunDateTime, the Dow and Nasdaq agents run. --  If the Dow or Nasdaq agents have run, the S&P 500 agents, Random agent, “Nearest Neighbor” agent and --  “Average Nearest Neighbor” agent will run. CREATE PROCEDURE spAgentsRunSomeIfNecessary @Symbol nvarchar(10) = NULL, @ForecastDate smalldatetime = NULL, @PriorRunDateTime datetime = NULL AS IF @Symbol IS NOT NULL AND @ForecastDate IS NOT NULL BEGIN DECLARE @AgentUserID int DECLARE @AgentID1 int, @AgentID2 int DECLARE @LatestPrice decimal(18, 8) DECLARE @MyForecast decimal(18, 8) DECLARE @DateFactor decimal(18,8) DECLARE @ForecastChange float DECLARE @Random float DECLARE @DowSymbol nvarchar(10), @NasdaqSymbol nvarchar(10), @SPSymbol nvarchar(10) DECLARE @Delta decimal(18,8)    SET @DowSymbol = ‘INDU.X’    SET @NasdaqSymbol = ‘COMPX.X’    SET @SPSymbol = ‘SPX.XO’ If @PriorRunDateTime Is Null BEGIN    -- Default = midnight today (12 AM this morning)    Declare @Today datetime, @SecondsSinceMidnight int    Set @Today = GetDate( )    Set @SecondsSinceMidnight = DatePart(hour, @Today) * 3600 + DatePart(minute, @today) * 60 + DatePart(second, @today)    Set @PriorRunDateTime = DateAdd( second, −@SecondsSinceMidnight, GetDate( ) ) END -- END If @PriorRunDateTime Is Null -- Run our agents if none have run -- since @PriorRunDateTime IF NOT EXISTS(Select Top 1 CreateDate FROM tblUserForecast    Where UserID IN (688, 689, 690, 691)    And Symbol=@Symbol    AND ForecastDate=@ForecastDate    AND CreateDate >= @PriorRunDateTime) BEGIN -- Running agents -- Set Common variables ------------    SET @LatestPrice = (SELECT TOP 1 Price FROM       tblMarketPrice WHERE Symbol = @Symbol       ORDER BY CreateDate DESC)    Set @DateFactor = DateDiff(d, GETDATE( ), @ForecastDate)    If @DateFactor < 1 Set @DateFactor = 1    Set @DateFactor = Log(@DateFactor) / 10 -- Done Setting Common variables -------    -- Agents can really only run if we have a current price for this stock ----    IF @LatestPrice IS NOT NULL    BEGIN -- spAgentDowPair -------------------    SET @AgentID1 = 690    SET @AgentID2 = 691 SET @Delta = (SELECT TOP 1 PercentChange / 100 FROM tblMarketPrice WHERE Symbol = @DowSymbol ORDER BY CreateDate DESC)    IF @Delta IS NOT NULL    BEGIN       -- Predict with the Dow       INSERT INTO tblUserForecast       (UserID, IP, Symbol, ForecastDate,         Forecast,       EntryOrder, EntryTool, CreateDate)       VALUES       (@AgentID1, ‘127.0.0.1’, @Symbol, @ForecastDate,         ( 1 + ( @Delta * (1+@DateFactor) ) ) * @LatestPrice,       NULL, NULL, GetDate( ))       -- Predict against the Dow       INSERT INTO tblUserForecast       (UserID, IP, Symbol, ForecastDate,         Forecast,       EntryOrder, EntryTool, CreateDate)       VALUES       (@AgentID2, ‘127.0.0.1’, @Symbol, @ForecastDate,         ( 1 + −1 * ( @Delta * (1+@DateFactor) ) ) * @LatestPrice,       NULL, NULL, GetDate( ))    END -- END IF @Delta IS NOT NULL -- Done with spAgentDowPair ------------------- -- spAgentNasdaqPair -------------------    SET @AgentID1 = 688    SET @AgentID2 = 689    SET @Delta = (SELECT TOP 1 PercentChange / 100 FROM tblMarketPrice WHERE Symbol = @NasdaqSymbol ORDER BY CreateDate DESC)    IF @Delta IS NOT NULL    BEGIN       -- Predict with the Nasdaq       INSERT INTO tblUserForecast       (UserID, IP, Symbol, ForecastDate,        Forecast,       EntryOrder, EntryTool, CreateDate)       VALUES       (@AgentID1, ‘127.0.0.1’, @Symbol, @ForecastDate,         ( 1 + ( @Delta * (1+@DateFactor) ) ) * @LatestPrice,       NULL, NULL, GetDate( ))       -- Predict against the Nasdaq       INSERT INTO tblUserForecast       (UserID, IP, Symbol, ForecastDate,         Forecast,       EntryOrder, EntryTool, CreateDate)       VALUES       (@AgentID2, ‘127.0.0.1’, @Symbol, @ForecastDate,         ( 1 + −1 * ( @Delta * (1+@DateFactor) ) ) * @LatestPrice,       NULL, NULL, GetDate( ))    END -- END IF @Delta IS NOT NULL -- Done with spAgentNasdaqPair -------------------       END -- END If @LatestPrice Is Not Null END ELSE IF NOT EXISTS(Select Top 1 CreateDate FROM tblUserForecast    Where UserID IN (680, 681, 692, 693, 699)    And Symbol=@Symbol    AND ForecastDate=@ForecastDate    AND CreateDate >= @PriorRunDateTime) BEGIN -- Running agents -- Set Common variables ------------    SET @LatestPrice = (SELECT TOP 1 Price FROM       tblMarketPrice WHERE Symbol = @Symbol       ORDER BY CreateDate DESC)    Set @DateFactor = DateDiff(d, GETDATE( ), @ForecastDate)    If @DateFactor < 1 Set @DateFactor = 1    Set @DateFactor = Log(@DateFactor) / 10 -- Done Setting Common variables -------    -- Agents can really only run if we have a current price for this stock ----    IF @LatestPrice IS NOT NULL    BEGIN -- spAgentSPPair -------------------    SET @AgentID1 = 692    SET @AgentID2 = 693    SET @Delta = (SELECT TOP 1 PercentChange / 100 FROM tblMarketPrice WHERE Symbol = @SPSymbol ORDER BY CreateDate DESC)    IF @Delta IS NOT NULL    BEGIN       -- Predict with the S&P 500       INSERT INTO tblUserForecast       (UserID, IP, Symbol, ForecastDate,         Forecast,      EntryOrder, EntryTool, CreateDate)      VALUES       (@AgentID1, ‘127.0.0.1’, @Symbol, @ForecastDate,         ( 1 + ( @Delta * (1+@DateFactor) ) ) * @LatestPrice,      NULL, NULL, GetDate( ))      -- Predict against the S&P 500      INSERT INTO tblUserForecast      (UserID, IP, Symbol, ForecastDate,         Forecast,       EntryOrder, EntryTool, CreateDate)       VALUES       (@AgentID2, ‘127.0.0.1’, @Symbol, @ForecastDate,         ( 1 + −1 * ( @Delta * (1+@DateFactor) ) ) * @LatestPrice,      NULL, NULL, GetDate( ))    END -- END IF @Delta IS NOT NULL -- Done with spAgentSPPair ------------------- -- spAgentAverageNN --------------    SET @AgentUserID = 681    SET @MyForecast = (SELECT AVG(ClosingPrice) FROM tblDailyPrice)    If @MyForecast Is Null Set @MyForecast = @LatestPrice    SET @ForecastChange = (@MyForecast − @LatestPrice) / @LatestPrice    SET @ForecastChange = @ForecastChange + (@ForecastChange * @DateFactor)    -- Don't forecast more than a 5% change...    IF @ForecastChange > .05 SET @ForecastChange = .05    IF @ForecastChange < −.05 SET @ForecastChange = −.05    SET @MyForecast = @LatestPrice * (1 + @ForecastChange)    -- Create our “forecast”    INSERT INTO tblUserForecast    (UserID, IP, Symbol, Forecast,     ForecastDate, EntryOrder, EntryTool, CreateDate) VALUES    (@AgentUserID, ‘127.0.0.1’, @Symbol, @MyForecast,     @ForecastDate, NULL, NULL, GETDATE( )) -- Done with spAgentAverageNN -------------- -- spAgentNN --------------    SET @AgentUserID = 680    -- Create our “forecast”    INSERT INTO tblUserForecast    (UserID, IP, Symbol, Forecast,     ForecastDate, EntryOrder, EntryTool, CreateDate)    VALUES (@AgentUserID,     ‘127.0.0.1’, @Symbol, @LatestPrice,     @ForecastDate, NULL, NULL, GETDATE( )) -- Done with spAgentNN -------------- -- spAgentRandom --------------    SET @AgentUserID = 699    -- Get our random float, seeding RAND with an int based off the current date.    SET @Random = .5 − RAND( (DATEPART(mm, GETDATE( )) * 100000 ) + (DATEPART(ss, GETDATE( )) * 1000 ) + DATEPART(ms, GETDATE( )) )    -- Now @Random is btw −.5 and .5... convert to a forecast change.    SET @ForecastChange = 1 + ( @Random / 50 )    -- Create our “forecast”    INSERT INTO tblUserForecast    (UserID, IP, Symbol, Forecast,     ForecastDate, EntryOrder, EntryTool, CreateDate)    VALUES (@AgentUserID,     ‘127.0.0.1’, @Symbol, @LatestPrice * @ForecastChange,     @ForecastDate, NULL, NULL, GETDATE( )) -- Done with spAgentRandom --------------    END -- END If @LatestPrice Is Not Null END -- END IF NOT EXISTS... END -- END IF @Symbol IS NOT NULL AND @ForecastDate IS NOT NULL

TABLE 2 Exemplary Code for Recent and Favorite Symbols (FavoriteSymbolsFunctions.asp) <% ‘ Copyright 2005 iQ Company Const FAVES_MaxFavoriteSymbols = 10 Sub AddFavoriteSymbols(SymbolsList)   Dim RecentSymbols, SymbolLocation   Dim RecentSymbolsList   Dim tmpVal, Itor   ‘ Read the RecentSymbols cookie, append those symbols with   ‘ our newly input list, and use GetSymbolListFromInputList to   remove duplicates   RecentSymbols = GetSymbolListFromInputList(SymbolsList   &“ ” & GetFavoriteSymbols( ))   If RecentSymbols <> “” Then     ‘ Enforce our FAVES_MaxFavoriteSymbols limit     RecentSymbolsList = Split(RecentSymbols, “,”)     If UBound(RecentSymbolsList)+1 >     FAVES_MaxFavoriteSymbols Then       RecentSymbols = “”       For Itor = 0 To FAVES_MaxFavoriteSymbols−1 Step 1         If RecentSymbols <> “” Then           RecentSymbols = RecentSymbols &“,”         End If         RecentSymbols = RecentSymbols & RecentSymbolsList(Itor)       Next     End If     ‘ Save our symbols     SetFavoriteSymbols RecentSymbols   End If End Sub Sub ClearFavoriteSymbols( )   SetFavoriteSymbols “” End Sub Sub RemoveFavoriteSymbol(Symbol)   Dim Favorites, NewFavorites, Length   Favorites = “,” &GetFavoriteSymbols( ) &“,”   NewFavorites = Replace(Favorites, “,” &Symbol &“,”, “,”)   If NewFavorites <> Favorites And Favorites <> “,,” Then     ‘ Symbol found (and removed)     If Len(NewFavorites) > 2 Then       ‘ Get rid of those extra “convenience commas” that we       added       Length = Len(NewFavorites)−2       NewFavorites = Mid(NewFavorites, 2, Length)     Else       NewFavorites = “”     End If     ‘ Write the new favorites     SetFavoriteSymbols NewFavorites   End If End Sub Function GetFavoriteSymbols( )   GetFavoriteSymbols = Request.Cookies(“FavoriteSymbols”) End Function Sub SetFavoriteSymbols(RecentSymbols)     ‘ Rewrite recent symbols cookie     Response.Cookies(“FavoriteSymbols”) = RecentSymbols     ‘ Expires in one month     Response.Cookies(“FavoriteSymbols”).Expires =     DateAdd(“m”, 1, CurrentEasternDateTime( )) End Sub %>

TABLE 3 Exemplary Code for Interface (pws_good_7pointinterface_working.asp) <% Option Explicit %> <!--#include virtual=“/asp/DateTimeFunctions.asp”--> <!--#include virtual=“/asp/Utilities.asp”--> <!--#include virtual=“/asp/DisplayFunctions.asp”--> <!--#include virtual=“/asp/FinWinFunctions.asp”--> <% ‘ Copyright 2005 iQ Company Dim SymbolList, SymbolArray, boolWeHaveNewSymbols Dim SymbolData, SymbolAwaitingPrediction, NewList Dim TheNextForecastDate, FriendlyNextForecastDate Dim UserID, AddOn, TotalSymbols, RequestedSymbols Dim ForecastLabels Const QuoteQueue = 10 ForecastLabels = Array(−10, −5, −2, −1, −0.5, 0, 0.5, 1, 2, 5, 10) boolWeHaveNewSymbols = False TheNextForecastDate = GetNextForecastDateTime(“d”, Now( )) FriendlyNextForecastDate = DisplayWeekday(TheNextForecastDate) UserID = GetUserID( ) If Request(“symbol”) <> “” Then   ‘   ‘ New Symbol(s) Requested   ‘   If Trim(Request(“new_list”)) = “” Then     AddOn = GetStarterList( )   Else     AddOn = Request(“new_list”)   End If   RequestedSymbols = GetSymbolListFromInputList(Request(“symbol”))   SymbolList = GetSymbolListFromInputList(RequestedSymbols &“,” &AddOn)   If SymbolList <> Request(“new_list”) Then     boolWeHaveNewSymbols = True   End If   ‘   ‘ Add these newly requested symbols to our user's favorites   ‘   AddFavoriteSymbols RequestedSymbols ElseIf Request(“new_list”) <> “” Then   SymbolList = GetSymbolListFromInputList(Request(“new_list”)) Else   SymbolList = GetStarterList( )   boolWeHaveNewSymbols = True End If SymbolArray = Split(SymbolList, “,”) TotalSymbols = UBound(SymbolArray) + 1 ‘Response.Write “<p>Symbol List: ” &SymboLList &vbCrLf &vbCrLf &“<p>New symbs? ” & boolWeHaveNewSymbols If boolWeHaveNewSymbols Then   GetSomeQuotes SymbolArray, TotalSymbols Mod QuoteQueue, False Else   ‘   ‘ Quotes not explicitly required... but we may still need them   ‘ (Normally we get quotes after the page loads... but sometimes   ‘ the page may not load all the way, so to prevent lacking data   ‘ we double-check that we have enough quotes for at least this page.   ‘   GetQuotesIfWeNeedThem SymbolArray, 3 End If ‘GetQuotesIfNecessary SymbolArray, boolWeHaveNewSymbols ‘ ‘ Load up the data for the first symbol needing a prediction ‘ If Request(“predicted_symbol”) <> “” Then   ‘   ‘ We have a prediction, so we will be displaying SymbolArray(0)   ‘ and SymbolArray(1) (the latter will be the symbol awaiting prediction)   ‘   Set SymbolData = GetSymbolDataFromAppSpace(“” &SymbolArray(1))   NewList = GetSymbolListFromInputList(Right(SymbolList, Len(SymbolList)− Len(SymbolArray(0))−1))   SymbolAwaitingPrediction = SymbolArray(1) Else   Set SymbolData = GetSymbolDataFromAppSpace(“” &SymbolArray(0))   NewList = SymbolList   SymbolAwaitingPrediction = SymbolArray(0) End If If SymbolData Is Nothing Then   ‘   ‘ Couldn't get quotes for this symbol   ‘   ‘ Remove it from our list of symbols   NewList = Right(NewList, Len(NewList)−Len(SymbolAwaitingPrediction)−1)   ‘ Also remove it from our favorites, if it's there   RemoveFavoriteSymbol SymbolAwaitingPrediction End If ‘ ‘ Display the page ‘ Response.Add Header “Expires”, 5 %><html> <head> <meta http-equiv=“content-type” content=“text/html; charset=UTF-8”> <title>Predict Wall Street</title> <link rel=“stylesheet” href=“/_include/standard.css” type=“text/css”> <style> <!-- body,td,div,.p,a{font-family:arial,sans-serif } div,td{color:#000} .f,.fl:link{color:#6f6f6f} a:link,.w,a.w:link,.w a:link{color:#00c} a:visited,.fl:visited{color:#551a8b} a:active,.fl:active{color:#f00} .t a:link,.t a:active,.t a:visited,.t{color:#000} .t{background-color:#e5ecf9} .k{background-color:#36c} .j{width:34em} .h{color:#36c} .i,.i:link{color:#a90a08} .a,.a:link{color:#008000} .z{display:none} div.n {margin-top: 1ex} .n a{font-size: 10pt; color:#000} .n .i{font-size: 10pt; font-weight:bold} .q a:visited., q a:link,.q a:active,.q {color: #00c; } .b{font-size: 12pt; color:#00c; font-weight:bold} .ch{cursor:pointer;cursor:hand} .e{margin-top: .75em; margin-bottom: .75em} .g{margin-top: 1em; margin-bottom: 1em} //--> </style> <META HTTP-EQUIV=“Expires” CONTENT=“0”> <META HTTP-EQUIV=“pragma” CONTENT=“no-cache”> <script language=“JavaScript” src=“_include/inpage_popup.js”></script> <script language=“JavaScript” src=“_include/overlay.js”></script> <STYLE> <!-- .popup { POSITION: absolute; VISIBILITY: hidden; BACKGROUND-COLOR: #eeeeee; LAYER-BACKGROUND-COLOR: #eeeeee; width: 300; BORDER-LEFT: 1px solid black; BORDER-TOP: 1px solid black; BORDER-BOTTOM: 3px solid black; BORDER-RIGHT: 3px solid black; PADDING: 3px; z-index: 10 } .meter { BACKGROUND-COLOR: #eeeeee; LAYER-BACKGROUND-COLOR: #eeeeee; BORDER: 1px solid black; PADDING: 3px; width: 380px; } .box { BORDER: 1px solid black; PADDING: 3px; width: 380px; } .prediction_cell { background-color: #eeeeee; border: 1px solid #eeeeee; } .highlight_cell { background-color: #ffffff; cursor: hand; border: 1px solid gray; } .prediction_link { text-decoration: none; color: black; } //--> </STYLE> <SCRIPT LANGUAGE=“JavaScript”> function bookmark(url, description) { netscape=“Netscape User's hit CTRL+D to add a bookmark to this site.” if (navigator.appName==‘Microsoft Internet Explorer’) { window.external.AddFavorite(url, description); } else if (navigator.appName==‘Netscape’) { alert(netscape); } } //--> </SCRIPT> </head> <body bgcolor=#ffffff text=#000000 link=#0000cc vlink=#551a8b alink=#ff0000 topmargin=3 marginheight=3> <form action=“<%=Request.ServerVariables(“SCRIPT_NAME”)%>” name=“QuickForm” method=“post” id=“QuickForm”> <!-- keep the popup divs as the first things on the page or else MSIE 5 on the mac sometimes has trouble rendering them on top of text --> <DIV onclick=‘event.cancelBubble = true;’ class=popup id=symbolSearchPopup> <table width=100% border=0 cellpadding=0 cellspacing=0 bgcolor=#eeeeee>  <tr>  <td bgcolor=#eeeeee> <table border=0 cellpadding=4 cellspacing=0>  <tr>  <td>  </td>  <td nowrap><font size=−1><b>Enter Stock Symbol(s)</b></font><br>   <input type=“text” name=“symbol” maxlength=255 size=“16”>   <input type=submit value=“Go”> <input type=submit name=lookup value=“Symbol Lookup”>   </td>  </tr>  </table>  </td>  <td valign=top align=right><a href=“#” onclick=“hideCurrentPopup( ); return false;”><img src=“images/close_x.gif” width=16 height=14 alt=“Click to close this mini window.” border=0></a></td>  </tr> </table>  </DIV> <input type=hidden name=new_list value=“<%=NewList%>”> </form> <% If Request(“predicted_symbol”) = “” Then   Response.Write “<center>” End If %> <a href=“/”><img src=“/images/logo.gif” width=“296” height=“26” border=“0” alt=“Predict Wallstreet”></a> <table width=100% border=0 cellpadding=0 cellspacing=0>  <tr>  <td bgcolor=#cccccc><img width=1 height=1 alt=“”></td>  </tr> </table> <font face=verdana,arial size=−2 color=#6f6f6f><%=Application(“QUOTE_DELAY_DISCLAIMER”) &“ ”%>   <%=PopupWindowLink(“<font face=verdana,arial color=#6f6f6f>Disclaimer</font>”, “/help/help.asp?text=” &Server.URLEncode(“Stock Quotes Disclaimer”) &“&src=” & Server.URLEncode(“/help/disclaimer.asp”), 250, 250)%>   </font> <div><img height=18 width=1 alt=“”></div> <form name=“prediction_form” action=<%=Request.ServerVariables(“SCRIPT_NAME”)%> method=post> <% If Request(“predicted_symbol”) <> “” Then   ‘ We have a prediction.   ‘ Display our ads, right aligned   Response.Write CreateAds( )   ‘ Next, display info regarding this prediction. %> <DIV onclick=‘event.cancelBubble = true;’ class=popup id=accuracy_info> <table width=100% border=0 cellpadding=0 cellspacing=0 bgcolor=#eeeeee>  <tr>  <td bgcolor=#eeeeee>   <%=GetAccuracyInsert( )%>   <p align=center><a href=“#” onclick=“hideCurrentPopup( ); return false;”>Close</a></p>  </td>  </tr> </table>  </DIV>  <table border=0 cellpadding=0 cellspacing=0 class=box><tr><td align=left>  <%=GetSymbolInfo(Request.Form(“predicted_symbol”), Request.Form(“predicted_name”))%><br><font face=verdana,arial size=−2 color=#6f6f6f>  Currently <%=DisplayDouble(Session(“CurrentPrice_” &SymbolArray(0)))%> -   You predicted <%=DisplayDouble(Request.Form(“prediction”))%>.   </font>  <div><img height=4 width=1 alt=“”></div>  <b><%=Session(“NumForecasters_” &SymbolArray(0))%> Others Predict: <font size=+1><%=DisplayDouble(Session(“CurrentForecast_” &SymbolArray(0)))%></font></b>  <font face=verdana,arial size=−2 color=#6f6f6f>for <%=FriendlyNextForecastDate%>'s Close &nbsp;&nbsp;&nbsp;<a href=“non_js_help.html” onclick=“return !showPopup(‘accuracy_info’, event, −100, −30);”>Accuracy?</a></font>  </td></tr></table>  <div><img height=30 width=1 alt=“”></div> <%   ‘ Clear those session variable   ‘Session(“CurrentPrice_” &SymbolArray(0)) = Empty   ‘Session(“NumForecasters_” &SymbolArray(0)) = Empty   ‘Session(“CurrentForecast_” &SymbolArray(0)) = Empty End If %> <!-- Done displaying forecast info --> <% Dim rstresults, strSearchString strSearchString = Trim(Request(“symbol”)) If Request(“lookup”) <> “” And strSearchString <> “” Then   ‘   ‘ Symbol Lookup mode   ‘   Set rstresults = DoLookup(strSearchString)   If rstresults Is Nothing Then     ‘ No symbols returned with this search. Print an informative warning. %>     <p><b>Your search for ‘<%=strSearchString%>’ returned no matches.</b>       <p>Some Suggestions:       <ul>        <li>Make sure all words are spelled correctly.</li>        <li>Try different keywords.</li>        <li>Try more general keywords.</li>       </ul> <%   Else %>     <p>The following closest match your search of ‘<%=strSearchString%>’.</p>     <table border=“0” cellspacing=“0” cellpadding=“0” class=meter>      <tr>      <td align=“left”>       <b>Symbol</b>      </td>      <td align=“left”>       <b>Name</b>      </td>      </tr> <%     Do While Not rstresults.EOF %>     <tr>      <td>      <a href=“<%=Request.ServerVariables(“SCRIPT_NAME”) &“?symbol=” & rstresults(“Symbol”)%>” onClick=“prediction_form.symbol.value = ‘<%=rstresults(“Symbol”)%>’; prediction_form.submit( ); return false;”><%=rstresults(“Symbol”)%></a>      </td>      <td>      <%=rstresults(“Issuer”)%>      </td>     </tr> <%       rstresults.MoveNext     Loop %>     </table> <%   End If ‘rstresults Is Nothing   ‘   ‘ Finally, display a symbol search form so you can search again if you like   ‘ %>   <p><font size=−1 ><b>Enter Stock Symbol(s)</b>:</font>   <input type=“text” name=“symbol” maxlength=255 size=“41”>   <input type=submit value=“Go”> <input type=submit name=lookup value=“Symbol Lookup”> <input type=submit name=Cancel value=“Cancel”> <% ElseIf SymbolData Is Nothing Then   ‘   ‘ SymbolAwaitingPrediction is apparently not a valid symbol   ‘   ‘ Prompt the user for action %> <p><b>‘<%SymbolAwaitingPrediction%>’ is an invalid stock ticker symbol.</b> <p><font size=−1><b>Symbol Lookup</b>:</font> <input type=“text” name=“symbol” maxlength=255 size=“41” value=“<%=SymbolAwaitingPrediction%>”> <input type=submit name=lookup value=“Symbol Lookup”> <input type=submit name=Cancel value=“Cancel” onClick=“prediction_form.symbol.value = ”; return true;”> <p> <% Else %> <!-- Prediction Interface --> <DIV onclick=‘event.cancelBubble = true;’ class=popup id=“symbol_info”> <%=ShowSymbolDetails(SymbolData)%> <div align=right><a href=“#” onclick=“hideCurrentPopup( ); return false;”>Close</a></div> </div>   <input type=hidden name=prediction value=“”>   <input type=hidden name=predicted_symbol value=“<%=SymbolData(“Symbol”)%>”>   <input type=hidden name=predicted_name value=“<%=SymbolData(“Name”)%>”>  <table border=0 cellpadding=0 cellspacing=0>   <tr>  <td><%=GetSymbolInfo(symbolData(“Symbols”), SymbolData(“Name”))%>&nbsp;&nbsp;</td>  <td>   <table border=0 cellpadding=0 cellspacing=0>   <tr>   <td><font size=−2><a href=“non_js_help.html” onclick=“return !showPopup(‘symbol_info’, event, −100, −30);”>Details</a></font></td>   </tr>   <tr>   <td><font size=−2><a href=“non_js_help.html” onclick=“return !showPopup(‘symbolSearchPopup’, event, −10, −30);”><b>Your</b> Stocks &raquo;</a></font></td>   </tr>   </table>  </td>   </tr>  </table>  <div><img height=4 width=1 alt=“”></div>  <table border=0 cellpadding=0 cellspacing=0>  <tr><td align=left>  <b>Today: <font size=+1><%=DisplayDouble(SymbolData(“Last”))%>&nbsp;</font></b><%=DisplayPercentChange (SymbolData(“PercentChange”))%>  <b><%=FriendlyNextForecastDate%>’s Close:&nbsp;<font size=+1>???</font></b>  </td></tr></table>   <div><img height=4 width=1 alt=“”></div> <%   DisplayPredictionInterface SymbolData(“Symbol”), SymbolData(“Last”), FriendlyNextForecastDate, ForecastLabels End If ‘ If SymbolData(“Symbol”) Is Nothing Then %>  <input type=hidden name=“new_list” value=“<%=NewList%>”>  <!-- End Prediction Area --> </form> <% If Request(“predicted_symbol”) = “” Then   Response.Write “</center>” End If %> <div><img height=12 width=1 alt=“”></div> <table width=100% border=0 cellpadding=0 cellspacing=0>  <tr>   <td bgcolor=#cccccc><img width=1 height=1 alt=“”></td>  </tr> </table> <p align=center>  <font size=−1>     <a href=/about.asp>About</a>     |      <a href=/contact.asp>Contact</a>      |      <a href=/terms.asp>Terms of Use</a>      <span id=hp style=“behavior:url(#default#homepage)”></span> <script> //<!-- if (!hp.isHomePage(‘http://www.predictwallstreet.com/’)) {document.write(“<p align=center><a href=\“/homepage.asp\” onClick=\“style.behavior=‘url(#default#homepage)’;setHomePage(‘http://www.predictwallstreet. com/’);\”>Make This Your Homepage!</a> | <a href=\“javascript:bookmark(‘http://www.predictwallstreet.com/’,‘Predict Wall Street’);\”>Bookmark this Site</A> | ”);} //--> </script> <a href=“tell_a_friend.asp”>Tell a Friend</a>  </font> </p>  <p align=center><font size=−2>&copy;<%=DatePart(“YYYY”, Now( ))%> iQ Company</font></p> <% If Request(“cache”) <> “” Then %> <script> <!--   // Preload the next page   var myImage = new Image;   myImage.src = “pws.asp”; //--> </script> <% End If %> </body> </html> <% Response.Flush ‘ ‘ Page display complete. ‘ ‘ ‘ Store our forecast (if we have one) ‘ If Request.Form(“predicted_symbol”) <> “” Then   If Application(“SESSION_STORED_FORECASTS”) Then     StoreForecastSession UserID, Request.Form(“predicted_symbol”), Request.Form(“prediction”), TheNextForecastDate   Else     StoreForecast UserID, Request.Form(“predicted_symbol”), Request.Form(“prediction”), TheNextForecastDate   End If End If ‘ ‘ Now run the agents for the currently-displayed symbol (if nec) ‘ and load the current forecast for this symbol into Application space ‘ If TypeName(SymbolData) = “Object” Or TypeName(SymbolData) = “IDictionary” Then   If Not (SymbolData Is Nothing) Then     Dim NumForecasters, CurrentForecast     GetForecastInfo SymbolAwaitingPrediction, TheNextForecastDate, NumForecasters, CurrentForecast     Session(“NumForecasters_” &SymbolAwaitingPrediction) = NumForecasters     Session(“CurrentForecast_” &SymbolAwaitingPrediction) = CurrentForecast     Session(“CurrentPrice_” &SymbolAwaitingPrediction) = SymbolData(“Last”)   End If End If ‘ ‘ Finally, get quotes for upcoming symbols if we need ‘em! ‘ If TotalSymbols Mod QuoteQueue <= 1 Then   GetSomeQuotes SymbolArray, QuoteQueue, True End If Function GetQuotesIfWeNeedThem(SymbolArray, MinimumPrequotedSymbols)   Dim tmpNumber, tmpSymbol, Itor   tmpNumber = MinimumPrequotedSymbols   If UBound(SymbolArray) < tmpNumber Then     tmpNumber = Ubound(SymbolArray) + 1   End If   For Itor = 0 To tmpNumber Step 1     tmpSymbol = SymbolArray(tmpNumber)     If NoSymbolData(tmpSymbol) Then       ‘ One of our first MinimumPrequotedSymbols       ‘ symbols doesn't have quote data... so just       ‘ get quotes for all MinimumPrequotedSymbols       GetSomeQuotes SymbolArray, tmpNumber, False       Exit Function     End If   Next End Function Function NoSymbolData(Symbol)   Dim ThisCreateDate   NoSymbolData = False   If TypeName(Application(“” &Symbol)) = “Object” Or TypeName(Application(“” & Symbol)) = “IDictionary” Then     If Application(“” &Symbol) Is Nothing Then       NoSymbolData = True     Else       ‘       ‘ Application(“” &Symbol) is an object...       ‘ but does it hold fresh enough data?       ‘       ThisCreateDate = Application(“” &Symbol)(“CreateDate”)       If 0 > DateDiff(“s”, Now( ), DateAdd(“n”, Application(“MINUTES_TO_STOCK_EXPIRATION”), ThisCreateDate)) Then         ‘ The current time is later than our “stale” date         NoSymbolData = True       End If     End If   Else     NoSymbolData = True   End If End Function Function GetSomeQuotes(SymbolArray, NumberToGet, boolSkipTheFirst)   Dim Itor, QuoteRequestList, NumSymbolsToQuote, ExtraOne, rstWhoCares   If NumberToGet > UBound(SymbolArray) Then     NumSymbolsToQuote = UBound(SymbolArray)   Else     NumSymbolsToQuote = NumberToGet   End If   ExtraOne = 1   If boolSkipTheFirst Then     ExtraOne = 0   End If   QuoteRequestList = “”   For Itor = 1 To NumSymbolsToQuote Step 1     If QuoteRequestList <> “” Then       QuoteRequestList = QuoteRequestList &“,”     End If     QuoteRequestList = QuoteRequestList &SymbolArray(Itor-ExtraOne)   Next   Set GetSomeQuotes = GetQuotes(QuoteRequestList, rstWhoCares)   ‘Response.Write “Getting quotes!” End Function Function GetQuotesIfNecessary(SymbolArray, boolWeHaveNewSymbols)   Dim TotalSymbols, TheModulus, NumSymbolsToQuote, Itor, QuoteRequestList, rstWhoCares   TotalSymbols = Ubound(SymbolArray)+1   TheModulus = TotalSymbols Mod 16   If boolWeHaveNewSymbols Or TheModulus = 8 Or TheModulus = 0 Then     ‘ This is our first time seeing these symbols     ‘ (e.g. either the first page load or the visitor     ‘ has requested custom symbols)     ‘   OR     ‘ We are due for new quotes (TheModulus = 0)     ‘ Get a list of the symbols that need quotes     ‘If TheModulus = 0 Then       NumSymbolsToQuote = 16     ‘Else       ‘ NumSymbolsToQuote = TheModulus     ‘End If     If NumSymbolsToQuote > UBound(SymbolArray) Then       NumSymbolsToQuote = UBound(SymbolArray)     End If     QuoteRequestList = “”     For Itor = 0 To NumSymbolsToQuote − 1 Step 1       If QuoteRequestList <> “” Then         QuoteRequestList = QuoteRequestList &“,”       End If       QuoteRequestList = QuoteRequestList &SymbolArray(Itor)     Next     Set GetQuotesIfNecessary = GetQuotes(QuoteRequestList, rstWhoCares)   Else     Set GetQuotesIfNecessary = Nothing   End If End Function Function ShowSymbolDetails(rstSymbolData)     ShowSymbolDetails = “<p class=g>” &vbCrLf &_(—)       “<div align=left><b>” &rstSymbolData(“Symbol”) & “</b>&nbsp;&nbsp;<font size=−1>(“ &rstSymbolData(“Name”) &”)</font><br> ” &vbCrLf &_(—)       “</div> ” &vbCrLf &_(—)       “<table style=““margin-top: 0.3em”” cellspacing=0 cellpadding=0 border=0> ” &vbCrLf &_(—)       “  <tr> ” &vbCrLf &_(—)       “  <td valign=top><img alt=“”“” src=“”/chart/get_chart.asp?s=“ & rstSymbolData(“Symbol”) &”“” width=212 height=102 border=0></td> ” &vbCrLf &_(—)       “  <td style=““padding-left: 0px; padding-bottom: 0px”” valign=center><table cellspacing=0 cellpadding=2 width=1% border=0> ” &vbCrLf &_(—)       “  <tr> ” &vbCrLf &_(—)       “   <td colspan=3 nowrap><font size=+1><b>” & DisplayDouble(rstSymbolData(“Last”)) & “&nbsp;</b></font>” & DisplayPriceChange(rstSymbolData(“Change”), rstSymbolData(“PercentChange”)) & “&nbsp;<font size=−1>&nbsp;” &DisplayLastTradeDateGeneric(rstSymbolData(“LTDate”), rstSymbolData(“LTTime”)) &“</font></td> ” &vbCrLf &_(—)       “  </tr> ” &vbCrLf &_(—)       “  <tr> ” &vbCrLf &_(—)       “   <td><table cellspacing=0 cellpadding=2 width=1% border=0> ” &vbCrLf &_(—)       “   <tr> ” &vbCrLf &_(—)       “    <td><font size=−1>Open:&nbsp;</font></td> ” &vbCrLf & _(—)       “    <td align=right><font size=−1>” & DisplayDouble(rstSymbolData(“Open”)) &“</font></td>” &vbCrLf &_(—)       “   </tr> ” &vbCrLf &_(—)       “   <tr> ” &vbCrLf &_(—)       “    <td><font size=−1>High:&nbsp;</font></td> ” &vbCrLf &_(—)       “    <td align=right nowrap><font size=−1>” & DisplayDouble(rstSymbolData(“High”)) &“</font></td>” &vbCrLf &_(—)       “   </tr> ” &vbCrLf &_(—)       “   <tr> ” &vbCrLf &_(—)       “    <td nowrap><font size=−1>Low:&nbsp;</font></td> ” & vbCrLf &_(—)       “    <td align=right nowrap><font size=−1>” & DisplayDouble(rstSymbolData(“Low”)) &“</font></td> ” &vbCrLf &_(—)       “   </tr> ” &vbCrLf &_(—)       “   </table></td> ” &vbCrLf &_(—)       “  <td width=20>&nbsp;</td> ” &vbCrLf &_(—)       “  <td><table cellspacing=0 cellpadding=2 width=1% border=0> ” &vbCrLf &_(—)       “   <tr>” &vbCrLf &_(—)       “   <td><font size=−1>Volume:&nbsp</font></td> ” &vbCrLf & _(—)       “   <td align=right><font size=−1>” & DisplayInt(rstSymbolData(“Volume”)) &“</font></td> ” &vbCrLf &_(—)       “   </tr> ” &vbCrLf &_(—)       “   <tr> ” &vbCrLf &_(—)       “   <td><font size=−1>P/E:&nbsp;</font></td> ” &vbCrLf &_(—)       “   <td align=right><font size=−1>” & DisplayDouble(rstSymbolData(“PE”)) &“</font></td> ” &vbCrLf &_(—)       “   </tr>” &vbCrLf &_(—)       “   <tr>” &vbCrLf &_(—)       “   <td><font size=−1>EPS:&nbsp;</font></td> ” &vbCrLf &_(—)       “   <td align=right><font size=−1>” & DisplayDouble(rstSymbolData(“EPS”)) &“</font></td> ” &vbCrLf &_(—)       “   </tr> ” &vbCrLf &_(—)       “  </table></td> ” &vbCrLf &_(—)       “  </tr> ” &vbCrLf &_(—)       “  <tr> ” &vbCrLf &_(—)       “   <td nowrap colspan=3><font face=verdana,arial size=−2 color=#6f6f6f>” &_(—)         GetExchange(rstSymbolData(“Exchange”)) &_(—)         “&nbsp;data&nbsp;delayed&nbsp;by&nbsp;” &_(—)         Delay(rstSymbolData(“Exchange”)) & “&nbsp;minutes&nbsp;- &nbsp;” &_(—)         PopupWindowLink(“<font face=verdana,arial color=#6f6f6f>Disclaimer</font>”, _(—)           “/help/help.asp?text=” &Server.URLEncode(“Stock Quotes Disclaimer”) &_(—)             “&src=” & Server.URLEncode(“/help/disclaimer.asp”), 250, 250) &_(—)       “     </a></font></td> ” &vbCrLf &_(—)       “   </tr> ” &vbCrLf &_(—)       “  </table></td> ” &vbCrLf &_(—)       “  </tr> ” &vbCrLf &_(—)       “</table> ” End Function Sub DisplayPredictionInterface(Symbol, CurrentPrice, FriendlyNextForecastDate, ForecastLabels)     Dim Label, Value, ForecastAmount, Counter     Dim SizePer, ThisLink, ThisForm, ThisDescription     ‘ Just to make sure...     CurrentPrice = CDbl(CurrentPrice) %>  <table class=meter>   <tr><td colspan=3 align=center>  <font size=−1><b>Please make a prediction to see what others predict.</b></font>  </td></tr><tr><td></td><td>  <table width=100% border=0 cellpadding=0 cellspacing=0>   <tr>  <%     SizePer = Round( 100 / ( 1 + UBound(ForecastLabels) ) )     For Each Value In ForecastLabels       Label = “”       If Value = 0 Then         Label = “&plusmn;0%”       Else         If Value > 0 Then           Label = “+”         End If         Label = Label &Value &“%”       End If       ForecastAmount = CurrentPrice + CurrentPrice * (Value / 100.0)       ThisForm = “document.prediction_form”       ThisLink = ThisForm & “.prediction.value = ” & ForecastAmount & “;” & ThisForm & “.submit( );”       ThisDescription = “Click if” &FriendlyNextForecastDate &“ ” & Symbol &“ will close at ” &DisplayDouble(ForecastAmount) &“ (” &Label &“)”       ‘       ‘ The old TD, which was storing forecasts twice! had an onclick value of ThisLink       ‘  %>   <td nowrap width=“<%=SizePer%>%” align=center class=prediction_cell onMouseOver=“this.className=‘highlight_cell’;” onMouseOut=“this.className=‘prediction_cell’;”><input type=radio name=“radio_<%=Counter%>” value=“<%=ForecastAmount%>” onClick=“<%=ThisLink%>” title=“<%=ThisDescription%>”><br><a href=“javascript: <%=ThisLink%>” onMouseOver=“window.status=‘<%=ThisDescription%>’; return true;” onMouseOut=“window.status=”; return true;” class=prediction_link title=“<%=ThisDescription%>”><font size=−2><%=Label%></font></a></td>  <%     Next ‘ For Each Value In ForecastLabels  %>   </tr>  </table></td><td></td></tr><tr><td><img src=“images/down_red.gif” width=14 height=11 border=0></td><td><table border=0 cellspacing=0 cellpadding=0 width=100%>       <tr height=5>       <td bgcolor=#F60900></td>       <td bgcolor=#E01F00></td>       <td bgcolor=#CA3500></td>       <td bgcolor=#B44B00></td>       <td bgcolor=#9E6100></td>       <td bgcolor=#867900></td>       <td bgcolor=#6E9100></td>       <td bgcolor=#56A900></td>       <td bgcolor=#3DC200></td>       <td bgcolor=#23DC00></td>       <td bgcolor=#0BF400></td>       </tr></table></td><td><img src=“images/up_green.gif” width=14 height=11 border=0></td></tr></table> <% End Sub Function GetSymbolDataFromAppSpace(Symbol)   On Error Resume Next   Err.Clear   Set GetSymbolDataFromAppSpace = Application(“” &Symbol)   If Err.Number <> 0 Then     Print “<p>Error in getting cached info for ” &Symbol &“: ” &Err.Number &“ - ” &Err.Description &“</p>”     Set GetSymbolDataFromAppSpace = Nothing     Err.Clear   End If End Function Function DisplayWeekday(SomeDate)   Dim Weekdays   Weekdays = Array(“”, “Sunday”, “Monday”, “Tuesday”, “Wednesday”, “Thursday”, “Friday”, “Saturday”)   Dim InputDate, Tomorrow   Tomorrow = FormatDateTime(DateAdd(“d”, 1, CurrentEasternDateTime( )), vbShortDate)   On Error Resume Next   InputDate = FormatDateTime(SomeDate, vbShortDate)   If Err.Number <> 0 Then     DisplayWeekday = “N/A”     Err.Clear   Else     If InputDate = Tomorrow Then       DisplayWeekday = “Tomorrow”     Else       DisplayWeekday = Weekdays(DatePart(“w”, InputDate))     End If   End If End Function Function CreateAds( )   CreateAds = “<table cellspacing=0 cellpadding=0 width=25% align=right bgColor=#ffffff border=0> ” &_(—)     “ <tr> ” &_(—)     “  <td colspan=4><font size=−1>&nbsp;</font></td> ” &_(—)     “ </tr> ” &_(—)     “ <tr> ” &_(—)     “  <td rowspan=5>&nbsp;&nbsp;</td> ” &_(—)     “  <td width=1 bgcolor=#c9d7f1 rowspan=5><img width=1 height=1 alt=“”“”></td> ” &_(—)     “  <td rowspan=5>&nbsp;&nbsp;</td> ” &_(—)     “  <td height=25 align=center><font color=#6f6f6f size=−1>Sponsored Links</font></td> ” &_(—)     “ </tr> ” &_(—)     “ <tr height=7> ” &_(—)     “  <td><img width=1 height=1 alt=“”“”></td> ” &_(—)     “ </tr> ” &_(—)     “ <tr> ” &_(—)     “  <td nowrap><font size=−1><a id=aw1 href=http://www.iqco.com>An iQ Innovation</a><br> ” &_(—)     “  Predict Wall Street is brought<br> ” &_(—)     “  to you by iQ Company.<br> ” &_(—)     “  <font class=a>www.iqco.com</font></font></td> ” &_(—)     “ </tr> ” &_(—)     “ <tr height=7> ” &_(—)     “  <td><img width=1 height=1 alt=“”“”></td> ” &_(—)     “ </tr> ” &_(—)     “ <tr> ” &_(—)     “  <td height=25 align=center><font size=−1></font></td> ” &_(—)     “ </tr> ” &_(—)     “</table>” End Function Function GetForecastInfo(Symbol, ForecastDate, ByRef NumForecasters, ByRef CurrentForecast)   Dim objConn, rstSymbols, SQL, Success   Success = False   ‘   ‘ Connect to the DB   ‘   Set objConn = Server.CreateObject(“ADODB.connection”)   objConn.Open Application(“DSN”)   Set rstSymbols = Server.CreateObject(“ADODB.RecordSet”)   ‘rstSymbols.CursorType = 2 ’adOpenDynamic   ‘rstSymbols.CursorLocation = 3 ’adUseClient   ‘   ‘ Run the agents if necessary, then grab our forecast info.   SQL = “EXEC spAgentsRunAllIfNecessary “‘ & Symbol & ’”, “‘ & ForecastDate & ’”;” & _(—)     “Select Symbol, ForecastDate, Avg(Forecast) as AvgForecast, Count(*) As NumberForecasts ” &_(—)     “from viewUserAndAnonForecasts Where ForecastDate = “‘ &ForecastDate & _(—)     ’” And Symbol = “‘ &Symbol &’” Group By Symbol, ForecastDate”   rstSymbols.Open SQL, objConn   If Not rstSymbols.EOF Then     ‘     ‘ Set NumForecasters     ‘     NumForecasters = rstSymbols(“NumberForecasts”)     ‘     ‘ Set CurrentForecast     ‘     CurrentForecast = rstSymbols(“AvgForecast”)     Success = True   End If   rstSymbols.Close   Set rstSymbols = Nothing   Set objConn = Nothing End Function Function GetSymbolInfo(Symbol, Name)   GetSymbolInfo = “<font size=+1>” & Symbol & “</font>&nbsp;<font size=−1>(“ &Name &”)</font>”   Select Case Symbol     Case “INDU.X”:       GetSymbolInfo = “<font size=+1>DOW JONES INDUSTRIAL AVERAGE</font>”     Case “SPX.XO”:       GetSymbolInfo = “<font size=+1>S&P 500 INDEX</font>”     Case “COMPX.X”:       GetSymbolInfo = “<font size=+1>NASDAQ COMPOSITE</font>”     Case “NYA.X”       GetSymbolInfo = “<font size=+1>NYSE COMPOSITE</font>”   End Select End Function Function StoreForecastSession(UserID, Symbol, Forecast, TheDate)   Dim ForecastHolder   Set ForecastHolder = Server.CreateObject(“Caprock.Dictionary”)   ForecastHolder.Add “Symbol”, Symbol   ForecastHolder.Add “Forecast”, Forecast   ForecastHolder.Add “Date”, TheDate   Set Session(“Forecasts”)(Session(“Forecast_Itor”)) = ForecastHolder   Session(“Forecast_Itor”) = Session(“Forecast_Itor”) + 1   If Session(“Forecast_Itor”) > Ubound(Session(“Forecasts”)) Then     ‘     ‘ This is a bad way to handle it...     ‘ but we can't do ReDim Preserve Session(“Forecasts”)(NewDimension)     ‘ because it generates Microsoft VBScript compilation error ‘800a0401’     ‘ (Expected end of statement)     ‘     Session(“Forecast_Itor”) = 0   End If End Function Function StoreForecast(UserID, Symbol, Forecast, TheDate)     ‘ TODO: add error checking for prediction and forecast date     ‘ (forecast date should be input variable).     Dim objCommand, objConn, EntryOrder, EntryTool     EntryOrder = 1     EntryTool = “ClickerInput 1”     Set objConn = Server.CreateObject(“ADODB.connection”)     objConn.Open Application(“DSN”)     Set objCommand = Server.CreateObject(“ADODB.Command”)     Set objCommand.ActiveConnection = objConn     objCommand.CommandType = 4 ‘const for a Stored Procedure     objCommand.CommandText = “spForecastUpdate”     If UserID = “” Then       ‘ Anonymous user (no User ID created yet)       objCommand.CommandText = “spForecastUpdateAnon”     Else       ‘       ‘ With this input method we are always considering predictors “anonymous”       ‘ We try our best with the UserID via Cookies and Session storage,       ‘ but it is unreliable.       ‘       ‘objCommand.CommandText = “spForecastUpdate”       objCommand.CommandText = “spForecastUpdateAnon”       objCommand.Parameters(1) = UserID     End If     objCommand.Parameters(2) = Request.ServerVariables(“REMOTE_ADDR”)     objCommand.Parameters(3) = Symbol     objCommand.Parameters(4) = Forecast     objCommand.Parameters(5) = TheDate     objCommand.Parameters(6) = EntryOrder     objCommand.Parameters(7) = EntryTool     ‘Response.Write “Saving ” &Symbol &“ @ ” &Forecast &“ on ” &TheDate & “<br>”     objCommand.Execute     ‘ If objCommand.Parameters(0) < 0 the forecast wasn't stored.     ‘ Otherwise, objCommand.Parameters(0) is our new UserID     If objCommand.Parameters(0) < 0 Then       ‘ Forecast storage failed (e.g. symbol not in our market price       ‘ table, or the forecast date has already passed)     Else       If UserID = “” Then         Session(“UserID”) = objCommand.Parameters(0)       End If     End If     Set objCommand = Nothing     objConn.Close     Set objConn = Nothing End Function Function GetUserID( )   If Session(“UserID”) = “” Then     ‘ No session-stored user id. Check for one in Cookies.     Session(“UserID”) = Request.Cookies(“PWS_User_ID”)     If Session(“UserID”) = “” Then       ‘ No UserID in a Cookie -- so we'll need to retrieve one.       GetUserID = “”     Else       ‘ User ID in Cookie. Great!       GetUserID = Session(“UserID”)     End If   Else     GetUserID = Session(“UserID”)   End If   If GetUserID <> “” Then     ‘ Always refresh our UserID cookie.     Response.Cookies(“PWS_User_ID”) = UserID     Response.Cookies(“PWS_User_ID”).expires = dateadd(“yyyy”,1,now)   End If End Function Function DoLookup(strSearchString)   Dim tmpURL, HttpObj, PostData, MyPacket, MyAdoConv   tmpURL = Application(“FINWIN_LOOKUP_URL”)   On Error Resume Next   Set HttpObj = Server.CreateObject(“SOFTWING.AspTear”)   PostData = “username=” &Application(“FINWIN_USER”) &_(—)     “&password=” &Application(“FINWIN_PASS”) &_(—)     “&id=” &Application(“FINWIN_ID”) &_(—)     “&request=lookup&Searchstring=” &Server.URLEncode(strSearchString)   MyPacket = HttpObj.Retrieve(tmpURL, _(—)     Application(“REQUEST_POST”), PostData, “”, “”)   ‘ Set up our recordset object   ‘Set rstresults = Server.CreateObject(“ADODB.Recordset”)   ‘ Get our data into a recordset object   ‘Set MyDeser = Server.CreateObject(“WDDX.Deserializer.1”)   Set MyAdoConv = Server.CreateObject(“WDDX.AdoConverter”)   Set DoLookup = MyAdoConv.deserialize(MyPacket)   If Err.Number <> 0 Then     ‘ Error somewhere, either in contacting FinWin,     ‘ creating object or (most likely) deserializing our packet.     ‘ Just return Nothing     Set DoLookup = Nothing   End If   Set MyAdoConv = Nothing   Set HttpObj = Nothing End Function Sub AddFavoriteSymbols(SymbolsList)   Dim RecentSymbols, SymbolLocation   Dim RecentSymbolsList   Dim tmpVal, Itor   ‘ Read the RecentSymbols cookie, append those symbols with our newly   ‘ input list, and use GetSymbolListFromInputList to remove duplicates   RecentSymbols = GetSymbolListFromInputList(SymbolsList &“ ” & GetFavoriteSymbols( ))   If RecentSymbols <> “” Then     SetFavoriteSymbols RecentSymbols   End If End Sub Sub RemoveFavoriteSymbol(Symbol)   Dim Favorites, NewFavorites, Length   Favorites = “,” &GetFavoriteSymbols( ) &“,”   NewFavorites = Replace(Favorites, “,” &Symbol &“,”, “,”)   If NewFavorites <> Favorites And Favorites <> “,,” Then     ‘ Symbol found (and removed)     If Len(NewFavorites) > 2 Then       ‘ Get rid of those extra “convenience commas” that we added       Length = Len(NewFavorites)−2       NewFavorites = Mid(NewFavorites, 2, Length)     Else       NewFavorites = “”     End If     ‘ Write the new favorites     SetFavoriteSymbols NewFavorites   End If End Sub Function GetFavoriteSymbols( )   GetFavoriteSymbols = Request.Cookies(“FavoriteSymbols”) End Function Sub SetFavoriteSymbols(RecentSymbols)     ‘ Rewrite recent symbols cookie     Response.Cookies(“FavoriteSymbols”) = RecentSymbols     ‘ Expires in one month     Response.Cookies(“FavoriteSymbols”).Expires = DateAdd(“m”, 1, Now( )) End Sub Function GetStarterList( )   Dim Favorites   Favorites = GetFavoriteSymbols( )   If Favorites <> “” Then     GetStarterList = GetSymbolListFromInputList(Favorites &“,” & Application(“DEFAULT_SYMBOL_LIST”))   Else     GetStarterList = “INDU.X,COMPX.X,GOOG,YHOO,GE,XOM,PFE,MSFT,C,WMT,AIG,INTC,BAC,JNJ,IBM,CSC O,PG,KO,MO,MRK,VZ,CVX,WFC,PEP,DELL,HD,LLY,JPM,UPS,SBC,AMGN,TWX,FNM,VIA,A BT,CMCSA,HPQ,MMM,AXP,ORCL,MDT,MWD,WB,ONEC,MER,WYE,QCOM,DIS,USB,GS,CO P,BMY,TXN,BLS,UTX,DD,LOW,BUD,UNH,TGT,G,FDC,DOW,MOT,BSX,WM,AMAT,MCD,WA G,ALL,BA,KRB,KMB,CAH,FITB,EMC,HON,CL,AA,STA,CAT,ADP,CCU,MET,EMR,NXTP,GM,I TW,SGP,CD,SYY,F,GCI,MMC,BK,PRU,IACI,FDX,LEH,EXC,SO,AFL,LMT,D,NCC,COX,GDT,IP ,NKE,GPS,SYK,STI,HCA,PGR,BAX,DUK,OXY,BBT,HIG,AVP,NOC,AMZN,GD,DE,GIS,COF,H DI,SLE,COST,SLM,BBY,NEM,WMI,FON,K,WLP,STT,TRB,DISH,AT,CFC,OMC,CAG,GDW,CM X,WY,SBUX,MHP,SCH,T,UNP,APA,CVS,DHR,PNC,DVN,KSS,A,APC,BR,HAL,SPLS,AET,MA S,MEL,JHF,CB,HNZ,RTN,ETR,FE,TJX,KR,BDX,PX,AEP,BHI,KEY,ATH,BNI,LXK,APD,PCG,FP L,MRO,LUV,BBBY,PFG,HSY,LTR,CCE,XRX,YUM,CLX,CPB,PGN,FO,ADM,AAPL,JCI,PEG,S, PPG,EOP,MAR,EL,PBI,PCAR,UCL,PCS,FD,MAY,SWY,ED,JCP,MON,EDS,LTD,MHS,GP,MC K,CI,CMA,TXU,ETN,ROH,AOC,BSC,NSC,DGX,LNC,ABS,HOT,HRB,DOV,CSC,MAT,AEE,AS D,PPL,JP,RF,CIT,EIX,LEN,PBG,VLO,DHI,ECL,TXT,AZO,EK,ITT,SRE,ACS,AVY,NYT,PD,PH, CIN,AV,XEL,CEG,DTE,IPG,NWL,TSN,CVC,LLL,ROK,RRD,CSX,DG,MGG,GPC,HLT,SAFC,AB C,HET,CTX,PHM,ESRX,FNF,KMP,ODP,AHC,KSE,MUR,FDO,JBL,MWV,SHW,AMD,CDWC,NI ,DPH,SANM,SII,MHK,RMK,WMB,DF,RSH,VFC,JWN,NTLI,NUE,RJR,AES,KMG,THC,GWW,W HR,AN,BDK,EPD,JNY,SUN,ROST,UIS,LEG,SLR,UNM,NCR,ORI,SSCC,EP,OCR,OHP,LEA,A W,CZR,HRL,MAN,SEE,SVU,X,LIZ,BC,BLL,DRI,HMT,KMRT,TDS,ALV,CVH,FL,SCG,EAT,EC,I SG,WEC,FSH,SPW,TOY,BER,CHRW,EAS,GR,SVM,TIN,CNP,KBH,NAV,EMN,HSIC,PHS,PO M,ASH,FLR,DCN,WC,AAP,ARW,HNT,KMX,PAS,SFD,AVT,HUM,RAD,CMI,LYO,CC,IM,R,PCO ,RBK,RKY,UHS,JEC,MYG,RRI,SKS,NU,TRI,CNO,GTW,TECD,AFG,BKS,FAF,OGE,TKR,AXL, OI,AFC,AG,AMR,BGP,MXO,IKN,RYL,TEX,BJ,BLI,CNF,CTB,WPS,YRK,BCO,CCK,CG,GT,HU G,PFGC,CMS,DDS,LI,USTR,ARM,TSO,VC,UAG,WIN,NWAC,OMI,SAH,DAL,KIND,CAL,GPI,L DG,LFG,OMG,SGR,AKS,USG,WCC,EME,IBC,TEN,CKC,NAFC,PTMK”   End If End Function Function GetAccuracyInsert( )   Dim StocksList, Stock   StocksList = Array(“All Stocks”, “A”, “GOOG”, “MSFT”, “YHOO”)   GetAccuracyInsert = “<table border=0 cellpadding=0 cellspacing=0><tr><td><img src=/chart/cache/680_400×240.gif width=400 height=240 border=0 alt=““Performance Chart””></td></tr>” &vbCrLf &_(—)     “<tr><td align=center><font size=−1><b>View Performance on:</b></font>&nbsp;<select name=““chart_stock””>”   for Each Stock in StocksList     GetAccuracyInsert = GetAccuracyInsert &vbCrLf &“<option value=“““ &Stock &”””>” &Stock &“</option>”   Next   GetAccuracyInsert = GetAccuracyInsert &vbCrLf &“</select></td></tr></table>” & vbCrLf &_(—)     “<font size=−1><p>Your performance will be charted here after market close on ” &FriendlyNextForecastDate &_(—)     “ </p><ul><li>Bookmark this site</li>” &vbCrLf &_(—)     “<li>Email performance info to: <input type=text size=10> <input type=button value=Submit><br>(Privacy Promise)</li></ul></font>” End Function %> 

1. A method for real-time on-line interactive forecasting of an element, the method comprising: identifying a first particular user who has accurately forecast a first element; determining, using a user forecasting accuracy performance based statistical algorithm, at least one second element to present to the first particular user when he attempts to forecast on the first element, the at least one second element being determined on a basis that other different users/contributors who had accurately forecast on the first element had also accurately forecast on the at least one second element; and proactively prompting the first user with the at least one second element when the user identifies a desire to forecast the first element, the proactively prompting of the at least one second element occurring automatically without the first user identifying the at least one second element.
 2. The method of claim 1, wherein the determining further comprising: quantifying a correlation between the first element and the at least one second element, and determining (i) that the at least one second element should be identified in the queue of elements for forecasting to present to the first particular user, and (ii) the ordered location of the at least one second elements in the queue of elements.
 3. The method of claim 1, wherein the method obtains the maximum useful information from the user with a minimum time and effort from the user.
 4. The method of claim 1, wherein the prompting of the first user with the at least one second element occurs at the time they are forecasting the first element.
 5. The method of claim 1, wherein the prompting is performed when the first user identifies the first element to be forecast.
 6. The method of claim 1, wherein the prompting is performed after the first user forecasts the first element.
 7. The method of claim 1, wherein the prompting is performed using a forecasting queue by inserting the at least one second element into the forecasting queue.
 8. The method of claim 1, wherein the prompting is performed using a forecasting queue by reordering the at least one second element to have a different position from the position before the reordering in the forecasting queue.
 9. The method of claim 1, wherein the prompting is performed using a forecasting queue by inserting the at least one second element into the forecasting queue at a particular position within a multi-element forecasting queue.
 10. The method of claim 1, wherein the prompting comprises inserting in an element forecast queue, or reordering to a higher position in the stock forecast queue when already present in a stock forecast queue, the at least one second element.
 11. The method of claim 1, wherein the at least one second element is in the same class or a related class to the first element.
 12. The method of claim 1, wherein the at least one second element consists of a second element.
 13. The method of claim 1, wherein the at least one second element comprises a plurality of second elements.
 14. The method of claim 1, wherein the prompt comprises a list with clickable web interface.
 15. The method of claim 1, wherein the at least one second element is related to the first element.
 16. The method of claim 15, wherein the relatedness is that the second element belongs to the same industry group as the first element.
 17. The method of claim 16, wherein the relatedness is that the second element belongs to the same industry group as the first element and the first element is an element for an Internet company.
 18. The method of claim 1, wherein the first element belongs to a first class of elements and the at least one second element belongs to the same first class of elements.
 19. The method of claim 1, wherein the element comprises at least one of a stock price or value, a commodity price or value, a bond price or value, and a security price or value.
 20. The method of claim 8, wherein an order or reordering of the elements in the queue are determined using collective intelligence analysis.
 21. The method of claim 8, wherein an order or reordering of the elements in the queue are determined using collaborative filtering.
 22. The method of claim 8, wherein an order or reordering of the elements in the queue are determined by statistical correlation methods for determining relationships between the elements.
 23. The method of claim 8, wherein an order or reordering of the elements in the queue are determined using a neural network approach.
 24. The method of claim 1, wherein the selection of the at least one second element is determined by a statistical correlation for determining relationships between the first element and the at least one second element.
 25. The method of claim 1, wherein the first element and second element are each selected from the set consisting of: a stock price, an option price, an ETF price, a mutual fund price, a commodities price, a currency exchange rate, a real estate price, an interest rate, a bond yield, a derivative, an insurance cost or price, a credit rating, a risk metric, a default rate, a news event, a sporting score, a bond price, a security price, an inventory figure, a sales figure, a consumer confidence estimate, a financial information, a vacation plan, a traffic route, an election result, a prediction of an action or actions by individuals, a prediction of an action or actions by groups, a prediction of an action or actions by companies, a prediction of an action or actions by governments, a prediction of an action or actions by an electorate, and combinations of any two or more of these.
 26. A computer implemented method for real-time on-line interactive forecasting of an element, the method comprising: receiving a request from a first particular user to forecast an element from a first client computer; identifying on a server computer in response to the received request that the first particular user has previously forecast a first element; determining, using a user forecasting accuracy performance based statistical algorithm executing in software on the second computer, at least one second element to present to the first particular user when he/he attempts to forecast on the first element, the at least one second element being determined on a basis that other different users/contributors who had historically accurately forecast on the first element had also historically accurately forecast on the at least one second element; and proactively prompting the first user with the at least one second element when the user identifies an intention to forecast on the first element, the proactively prompting of the at least one second element to the particular first user occurring automatically without the first user identifying the at least one second element.
 27. The method of claim 26, wherein the determining comprising quantifying a correlation between the first element and the at least one second element, and determining (i) that the at least one second element should be identified in the queue of elements for forecasting to present to the first particular user, and (ii) the ordered location in the queue of elements for forecasting.
 28. The method of claim 26, wherein at least one of the following: (i) the prompting the of the first user with the at least one second element occurs at the time they are forecasting the first element, (ii) the prompting is performed when the first user identifies the first element to be forecast; (iii) the prompting is performed after the first user forecasts the first element; (iv) the prompting is performed using a forecasting queue by inserting the at least one second element into the forecasting queue; (v) the prompting is performed using a forecasting queue by reordering the at least one second element to have a different position from the position before the reordering in the forecasting queue; (vi) the prompting is performed using a forecasting queue by inserting the at least one second element into the forecasting queue at a particular position within a multi-element forecasting queue; and (vii) the prompting comprises inserting in an element forecast queue, or reordering to a higher position in the stock forecast queue when already present in a stock forecast queue, the at least one second element.
 29. The method of claim 26, wherein at least one of the following applies: (i) the at least one second element is in the same class or a related class to the first element; (ii) the at least one second element comprises a second element; and (iii) the at least one second element comprises a plurality of second elements.
 30. The method of claim 26, wherein the prompt comprises a list with clickable web interface.
 31. The method of claim 26, wherein the at least one second element is related to the first element; the relatedness is that the second element belongs to the same industry group as the first element; and the relatedness is that the second element belongs to the same industry group as the first element and the first element is an element for an Internet company.
 32. The method of claim 28, wherein the prompting is performed using ordering or reordering and an order or reordering of the elements in the queue are determined using at least one of (i) collective intelligence analysis, (ii) using collaborative filtering, (iii) statistical correlation methods for determining relationships between the elements, and (iv) a neural network approach.
 33. The method of claim 26, wherein identifying on a server computer in response to the received request that the first particular user has previously accurately forecast a first element.
 34. A system for real-time on-line interactive forecasting of an element, the system comprising: a server configured for receiving a request from a first particular user to forecast an element from a first client computer; a database storing historical forecast information for a plurality of users and for particular forecast elements; means for identifying on the server computer in response to the received request and the historical forecast information that the first particular user has previously accurately forecast a first element; means for determining, using a user forecasting accuracy performance based statistical algorithm executing in software on the server computer and accessing the database, at least one second element to present to the first particular user when he/she attempts to forecast on the first element, the at least one second element being determined on a basis that other different users/contributors who had historically accurately forecast on the first element had also historically accurately forecast on the at least one second element; and means for proactively sending a prompt to the first user on the first client computer with the at least one second element when the server computer receives a user intention to forecast on the first element, the proactively prompting of the at least one second element to the particular first user occurring automatically without the first user identifying the at least one second element.
 35. The system of claim 34, wherein the means for determining further comprises a correlator for quantifying a correlation between the first element and the at least one second element and for determining (i) that the at least one second element should be identified in the queue of elements for forecasting to present to the first particular user, and (ii) the ordered location in the queue of elements for forecasting.
 36. A method for real-time on-line interactive forecasting of an element, the method comprising: receiving a plurality of different user inputs for a forecast of an element; capturing the plurality of different user input contributions for the forecast of the element; generating an updated collective contributed forecast information based on the plurality of different user inputs for the forecast of the element as each different user input contribution is received; and sending the updated collective contributed forecast information back to each user who made an input contribution.
 37. The method of claim 36, further comprising: identifying a first particular user who has accurately forecast a first element; determining, using a user forecasting performance based statistical algorithm, at least one second element to present to the first particular user when he attempts to forecast on the first element, the at least one second element being determined on a basis that other different users/contributors who had accurately forecast on the first element had also accurately forecast on the at least one second element; and proactively prompting the first user with the at least one second element when the user identifies a desire to forecast the first element, the proactively prompting of the at least one second element occurring automatically without the first user identifying the at least one second element.
 38. The method of claim 36, further comprising: identifying a first particular user who has accurately forecast a first element; determining, using a user forecasting performance based statistical algorithm, at least one second element to present to the first particular user when he attempts to forecast on the first element, the at least one second element being determined on a basis that other different users/contributors who had accurately forecast on the first element had also accurately forecast on the at least one second element; and proactively prompting the first user with the at least one second element when the user identifies a desire to forecast the first element, the proactively prompting of the at least one second element occurring automatically without the first user identifying the at least one second element.
 39. A computer program stored on a computer readable medium for execution on a computer that when executed in a processor of the computer executes a method for real-time on-line interactive forecasting of an element, the method comprising: Identifying, in a first server computer, a first particular user who has accurately forecast a first element; determining, in a first server computer or in a second server computer, using a user forecasting accuracy performance based statistical algorithm, at least one second element to present to the first particular user when he attempts to forecast on the first element, the at least one second element being determined on a basis that other different users/contributors who had accurately forecast on the first element had also accurately forecast on the at least one second element; and proactively prompting the first user on a user computer different from said first and second server computer, with the at least one second element when the user identifies a desire to forecast the first element, the proactively prompting of the at least one second element occurring automatically without the first user identifying the at least one second element.
 40. A system for real-time on-line interactive forecasting of an element, the system comprising: a pre-queuing block for queuing a list of elements for fast forecasting an element; a receiver block for receiving a plurality of different user input for a forecast of an element; a capture block for capturing the plurality of different user inputs for the at least one forecast of an element; a storage device for storing the captured plurality of different user inputs for the at least one forecast element, a generator device for generating a collective consensus contributed forecast information based on a plurality of different user contributed forecast inputs; and a communications device for sending the collective consensus contributed forecast information back to the user who originally sent the input. 